update-ignored-endpoints

Update IGNORED_ENDPOINTS.md by analyzing API client files and MCP tools.

2|3|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/umbraco/Umbraco-MCP-Base --skill update-ignored-endpoints
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-ignored-endpoints
Source: https://github.com/umbraco/Umbraco-MCP-Base/tree/main/plugins/skills/update-ignored-endpoints
Command: npx skills add https://github.com/umbraco/Umbraco-MCP-Base --skill update-ignored-endpoints

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the tedious process of manually tracking which API endpoints are implemented as MCP tools versus those that are intentionally ignored, ensuring documentation stays accurate and reflects the current state of API coverage.

Core Features & Use Cases

  • Automated Discovery: Scans generated API client files and implemented MCP tools to identify endpoint coverage.
  • Documentation Generation: Updates the IGNORED_ENDPOINTS.md file with current statistics and categorized lists of unimplemented endpoints.
  • Use Case: After implementing new MCP tools for Umbraco's Forms API, run this skill to automatically update the documentation, showing which Forms API endpoints are now covered and which remain ignored, providing a clear overview of implementation progress.

Quick Start

Run the command to update the ignored endpoints documentation.

Frequently Asked Questions about update-ignored-endpoints

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate tracking unimplemented API endpoints in documentation?

Automating API endpoint coverage tracking involves scanning generated API client files and comparing them against implemented MCP tools to update the IGNORED_ENDPOINTS.md file with categorized lists and statistics.

What is the best way to keep API endpoint docs current after adding new MCP tools?

Keeping API endpoint docs current is done by analyzing TypeScript API client Result type exports and scanning the tools directory to categorize and document newly implemented or ignored endpoints.

How does endpoint coverage discovery work for MCP tools?

Endpoint coverage discovery works by scanning generated API client files for Result type exports and matching them against the implemented MCP tools directory to identify which endpoints remain unimplemented.

Does updating ignored endpoints documentation preserve existing rationale sections?

Updating ignored endpoints documentation preserves existing rationale sections while appending current statistics and categorized lists of unimplemented endpoints discovered during the API client scan.

Can I use this endpoint documentation automation without dependencies?

Yes, this endpoint documentation automation runs without external dependencies, requiring only generated API client files and an implemented MCP tools directory to generate the coverage documentation.

Why should I generate documentation automation for ignored API endpoints?

Generating documentation automation for ignored API endpoints eliminates manual tracking errors, providing a clear overview of implementation progress and which Forms API endpoints remain intentionally ignored.