Narrareach

Get an article brief

get_article_brief

Read-onlyIdempotent

One article brief and its draft status. After queue_article_draft, call this about every 30 seconds until status is READY (draftUrl opens the draft) or FAILED. A draft usually takes 1 to 3 minutes. Available on the Revenue Writer plan and above.

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": {
      "briefId": "<briefId>"
    },
    "name": "get_article_brief"
  }
}

Input Schema

Name	Required	Description	Default
`briefId`	Yes	A brief id from generate_article_briefs or list_article_briefs.

Output Schema

Name	Required	Description	Default
`id`	Yes
`title`	Yes
`pillar`	Yes
`source`	Yes
`status`	Yes
`whyNow`	Yes
`batchId`	Yes
`draftId`	Yes
`outline`	Yes
`draftUrl`	Yes
`evidence`	Yes
`question`	Yes
`createdAt`	Yes
`expiresAt`	Yes
`failureCode`	Yes
`connectedAccount`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the annotations, the description discloses polling cadence, expected latency of 1 to 3 minutes, status values, the meaning of draftUrl, and a plan availability requirement. This is rich behavioral context for a read-only getter.

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?

The description is short, front-loads the tool's resource, and then adds only operational details the agent needs: polling cadence, latency, and plan gating. Every sentence earns its place.

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?

With an output schema, full schema description coverage, and clear annotations, the description supplies the remaining operational context an agent needs: when to poll, how often, how long to expect, and plan availability. Nothing material is missing for correct invocation.

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 schema already explains that briefId comes from generate_article_briefs or list_article_briefs. The description adds no parameter-level detail, so the baseline of 3 is appropriate.

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?

The description clearly indicates retrieval of a single article brief plus its draft status, and the singular wording implicitly contrasts with list_article_briefs. However, it does not explicitly name sibling tools or distinguish itself from them by name, so it falls short of a 5.

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?

It gives a strong, explicit usage context: call after queue_article_draft, poll about every 30 seconds, and stop at READY or FAILED. It does not explicitly route the agent away from alternatives such as list_article_briefs, so it stops short of a 5.

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

All Narrareach 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?