DevTune MCP

devtune_close_draft_pull_request

DestructiveIdempotent

Close the open pull request DevTune opened from an action's draft and delete DevTune's branch, or archive its GitBook change request, as the member who created the API key or authorized this connection; they must manage this project. Works even when content pull requests are no longer enabled, so a pull request can always be withdrawn. The draft stays. Refusals: no_pull_request, pull_request_merged, source_needs_reconnect (reconnect GitHub or GitBook, or close it there), github_error and gitbook_error. Returns the closed pull request.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "actionId": "<actionId>"
    },
    "name": "devtune_close_draft_pull_request"
  }
}

Input Schema

Name	Required	Description	Default
`actionId`	Yes	UUID of the action.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already flag destructive/openWorld/idempotent, and the description still adds real substance: it states that 'The draft stays' (defining what is and is not destroyed), the permission scope required, the invariance condition for allowed state, the full refusal enum with remedies, and the return value. That is exactly the beyond-annotation context a caller needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key action and scope are front-loaded, and the refusal list is compact and scannable. The opening sentence is long and stacks two distinct targets (GitHub pull request and GitBook change request), which slightly slows parsing, but nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter destructive tool with no output schema, the definition covers the required authorization, the side effects, the failure modes with remedies, and the return value. Nothing an agent needs in order to call it safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single actionId is fully documented in the schema, so baseline applies. The description does tie the parameter to the subject ('an action's draft'), confirming the ID identifies the action whose PR is closed, but adds no format or selection guidance beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Close the open pull request DevTune opened from an action's draft and delete DevTune's branch, or archive its GitBook change request'), making clear it is the inverse of devtune_create_draft_pull_request. The dual GitBook/GitHub target is stated explicitly, so an agent can distinguish it from any sibling without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear authorization context ('as the member who created the API key or authorized this connection; they must manage this project') plus an edge case where it still applies ('Works even when content pull requests are no longer enabled'). Refusal codes double as when-cannot-use conditions with a fallback ('reconnect GitHub or GitBook, or close it there'), but no sibling tool is named as an alternative path.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All DevTune MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?