Retrieve a specific attempt of a GitHub Actions workflow run using owner, repo, run ID, and attempt number. Optionally exclude pull requests from the response.
Get a workflow run attempt
| Name | Required | Description | Default |
|---|---|---|---|
| owner | Yes | owner | |
| repo | Yes | repo | |
| run_id | Yes | run_id | |
| attempt_number | Yes | attempt_number | |
| exclude_pull_requests | No | If `true` pull requests are omitted from the response (empty array). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description only implies a read operation but lacks details on safety, authentication requirements, error handling, or output structure. With no annotations, this is insufficient.
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?
The description is extremely concise (one sentence) but under-specified. While not verbose, it sacrifices completeness for brevity.
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?
Given no output schema and no annotations, the description should explain what a workflow run attempt is and how it differs from a run. It is incomplete.
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%, so the baseline is 3. The description adds no additional meaning beyond the parameter names and brief schema descriptions.
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?
The description 'Get a workflow run attempt' clearly states the action and resource, but does not differentiate from siblings like 'github_actions_get_workflow_run' or 'github_actions_get_workflow_run_usage'.
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?
No guidance is provided on when to use this tool versus alternatives such as 'github_actions_get_workflow_run' or 'github_actions_list_workflow_runs'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Eyalm321/github-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server