Skip to main content
Glama

List DraftRoom Manual drafts

list_expressroom_drafts
Read-onlyIdempotent

List Manual DraftRoom drafts before they are promoted to official Jobs; filter by status or locate drafts via Jobs Board todo ID, PR number/URL, or mirrored job name.

Instructions

Lists Manual DraftRoom drafts. These are draft-only records until promoted into official Jobs. Use official_todo_id or official_job_mirror to find drafts linked to a Jobs Board card, PR number, PR URL, or mirrored job name.

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>"
    },
    "name": "list_expressroom_drafts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
agent_idYesStable identifier for the calling agent.
express_statusNoOptional status filter.
official_todo_idNoOptional exact Jobs Board todo UUID mirror.
official_job_mirrorNoOptional fuzzy mirror search text, such as job name, PR number, PR URL, or todo id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive behavior, and closed-world scope. The description adds useful lifecycle context: these are draft-only records until promoted into official Jobs, which helps the agent understand the data state.

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

Conciseness5/5

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

Three compact sentences with the core purpose front-loaded, followed by lifecycle context and filter guidance. No filler or redundant restatement.

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

Completeness4/5

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

Covers purpose, draft lifecycle, and the key mirror filters. It omits mention of the express_status filter and pagination/limit behavior, but annotations cover the safety profile and the schema documents those parameters reasonably well.

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 80%, so the baseline is 3. The description adds linking semantics for official_todo_id and official_job_mirror, but does not mention express_status, limit, or agent_id, leaving those to the schema.

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?

States a specific verb and resource ("Lists Manual DraftRoom drafts") and distinguishes these records from official Jobs by noting they are draft-only until promoted. An agent can tell this is for draft records rather than official job/todo listings.

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

Usage Guidelines3/5

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

Explains that official_todo_id and official_job_mirror can be used to find drafts linked to Jobs Board cards, PRs, or job names, which clarifies filter usage. However, it does not explicitly name when to choose this tool over siblings like list_todos, list_actionable_todos, create_expressroom_draft, or promote_expressroom_draft.

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