Skip to main content
Glama

Update a plan brief

update_plan_brief

Rewrite the brief a plan's agents work from: objective, audience, platforms, and the dense context pack (summary/position/claims). This changes what the planner would produce next; it does not regenerate assets on its own.

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": {
      "plan_id": "<plan_id>"
    },
    "name": "update_plan_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
claimsNo3–5 factual statements the assets may make
plan_idYes
objectiveNo
platformsNo
context_summaryNoThe position in dense prose — what every asset is briefed from
target_audienceNo
context_positionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnly=false, idempotent=false, destructive=false; the description adds the real behavioral payload — the edit propagates into future planner output but does not itself produce assets. It omits whether this is a partial or full replacement write, which matters given idempotentHint=false and only plan_id being required.

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?

Two sentences, no filler, with the resource and scope front-loaded and the caveat about non-regeneration placed where it is most needed. Every clause carries information.

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 an eight-parameter mutation with no output schema and thin schema descriptions, the definition covers intent and downstream effect but leaves the update semantics (partial vs. full overwrite, behavior of unset fields) unresolved. An agent could call it correctly only by guessing those semantics.

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 only 25%, and the description compensates for part of it by grouping the fields into named concepts (objective, audience, platforms, context summary/position/claims). It says nothing about `name`, `plan_id`, or — critically — whether omitted fields are preserved or cleared, leaving half the parameters undocumented in both places.

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?

"Rewrite the brief a plan's agents work from" gives a specific verb and a specific resource, then enumerates the surface it covers (objective, audience, platforms, context pack). The closing clause draws a clear boundary against asset-regenerating siblings such as execute_content_plan or update_content_asset.

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 states the downstream effect ("changes what the planner would produce next") and explicitly excludes regenerating assets, which effectively tells the agent to use this before re-running the planner rather than instead of it. It stops short of naming the sibling tool to call for regeneration or any prerequisites/ordering constraints.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources