Skip to main content
Glama

Insert DraftRoom draft into Jobs

promote_expressroom_draft

Create an official Boardroom job from a Manual DraftRoom draft and link both records, while preserving any blocker and next build step for follow-up integration and review.

Instructions

Creates an official Boardroom job from a Manual DraftRoom draft and links the two records. If the warm chat seat did not supply code, keep the exact blocker and next build step visible. The new job still needs normal UnClick integration, tests, PR or commit proof, and review.

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": {
      "agent_id": "<agent_id>",
      "draft_id": "<draft_id>"
    },
    "name": "promote_expressroom_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesStable identifier for the calling agent.
draft_idYesDraftRoom draft id.
priorityNonormal
force_newNoCreate a new job even if this draft already has a linked official job.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world behavior. The description adds useful context about linking two records and keeping blocker/next-step information visible, but does not disclose return shape, authentication requirements, rate limits, or what force_new actually does beyond the schema's own description.

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?

Three concise sentences with the primary action front-loaded. The second and third sentences are somewhat opaque but not wasted; they add domain-specific operational context without padding.

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

Completeness3/5

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

For a mutation tool with no output schema and four parameters, the description covers purpose and downstream workflow needs but omits what the tool returns (e.g., new job id, link status) and any authorization or duplicate-handling semantics. It is adequate but leaves meaningful gaps.

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 description coverage is 75%, so most parameters are already documented. The description adds no parameter-level meaning and does not compensate for the undocumented priority enum. Baseline 3 is appropriate given that the schema carries most of the semantic load.

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

Purpose4/5

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

States a specific verb+resource: 'Creates an official Boardroom job from a Manual DraftRoom draft and links the two records.' This distinguishes it from create_expressroom_draft (creates a draft) and promote_idea_to_todo. Domain jargon ('Boardroom', 'warm chat seat') slightly muddies the read, but the core action is unmistakable.

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

Usage Guidelines2/5

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

The description never states when to use this tool versus alternatives like create_expressroom_draft, list_expressroom_drafts, or promote_idea_to_todo. The conditional 'If the warm chat seat did not supply code...' is a behavioral instruction, not usage guidance, and no prerequisites or exclusions are named.

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

Deploy Server

Other Tools