Fetch the status of recent CI/CD pipeline runs from GitHub Actions, optionally filtering by branch or status to monitor build health.
Fetches the status of recent CI/CD pipeline runs from GitHub Actions. Optionally filter by branch or status.
| Name | Required | Description | Default |
|---|---|---|---|
| branch | No | Filter by branch name (e.g., "main") | |
| status | No | Filter by pipeline status |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, so the description carries the full behavioral burden. It does not disclose the window of 'recent', pagination, rate limits (GitHub API), authentication requirements, or output shape. Read-only intent is implied by 'Fetches' but nothing more.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences with the primary action front-loaded and the optional filters noted second. Nothing redundant.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a list-fetch tool with no annotations and no output schema, the description should clarify the time window, volume, and return format. None of that is present, leaving key invocation context missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and already documents both parameters with examples and an enum. The description only restates that filtering is optional, adding no syntax or default-window details beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clear verb 'Fetches' and resource 'status of recent CI/CD pipeline runs' with source 'GitHub Actions'. Siblings are all unrelated monitoring/security tools, so no differentiation is needed, but 'recent' is vague without a defined window.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Hints that branch and status filters are optional and that omitting them returns recent runs, but gives no guidance on when to use this versus any monitoring sibling (e.g., prometheus metrics, k8s events) or any exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.