Skip to main content
Glama

Update the action plan

manage_actions

Close or dismiss an action-plan item (action_id from get_actions), or add the user's own action. operation: done = mark it done; dismiss = dismiss it (reversible in the app); create = add the user's own action (title, type, priority, prompts, detail). Without confirm: true NOTHING changes: you get a preview. Show it to the user and call again with confirm: true only after they approve it.

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": {
      "operation": "<operation>"
    },
    "name": "manage_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOnly for operation create. Action type, as in get_actions kind.
brandNoBrand id, name or domain (from get_account (view: brands)). Optional when the account has a single brand.
titleNoOnly for operation create. What to do, e.g. "Get listed on the G2 comparison page".
detailNoOnly for operation create. Steps or context (optional).
confirmNoLeave out (or false) to get a preview: nothing changes. Set true ONLY after the user approved that exact preview.
promptsNoOnly for operation create. Tracked questions it serves (optional).
priorityNoOnly for operation create. Default Medium.
action_idNoOnly for operation done, dismiss. Action id, e.g. offpage:g2.com or content:<prompt>.
operationYesWhat to do.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / action_id / description
      Previous value: -"Action id, e.g. offpage:g2.com or content:<prompt>."New value: +"Only for operation done, dismiss. Action id, e.g. offpage:g2.com or content:<prompt>."
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "Only for operation create. Steps or context (optional).",
      +  "type": "string"
      +}
    • changedInput schema / properties / operation / enum
      Previous value: -[
      -  "done",
      -  "dismiss"
      -]New value: +[
      +  "done",
      +  "dismiss",
      +  "create"
      +]
    • addedInput schema / properties / priority
      Added value: +{
      +  "description": "Only for operation create. Default Medium.",
      +  "enum": [
      +    "High",
      +    "Medium",
      +    "Low"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / prompts
      Added value: +{
      +  "description": "Only for operation create. Tracked questions it serves (optional).",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / title
      Added value: +{
      +  "description": "Only for operation create. What to do, e.g. \"Get listed on the G2 comparison page\".",
      +  "type": "string"
      +}
    • addedInput schema / properties / type
      Added value: +{
      +  "description": "Only for operation create. Action type, as in get_actions kind.",
      +  "enum": [
      +    "content_gap",
      +    "content",
      +    "refresh",
      +    "offpage",
      +    "technical",
      +    "setup",
      +    "links",
      +    "pruning"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "operation",
      -  "action_id"
      -]New value: +[
      +  "operation"
      +]
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, it discloses the most important behavioral trait: without confirm: true nothing changes and the caller only gets a preview that must be shown to the user and approved. It also notes dismiss is reversible in the app, which is meaningful context not carried by destructiveHint=false.

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?

Dense and front-loaded: the confirm gate is stated twice for emphasis, which is justified for a mutation tool, though the semicolon-chained operation list reads a little terse and could be structured more cleanly.

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?

For a 9-parameter mutating tool with no output schema and no annotations covering destructive behavior, the description covers the essential contract: which operations exist, which fields apply, and that nothing mutates before confirmation. Only the shape of the preview response is left unexplained.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning by tying the operation enum values to outcomes and clarifying that title/type/priority/prompts/detail belong to create only. The confirm parameter's role is reinforced with its gating semantics rather than merely restated.

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?

The opening sentence states a concrete verb set (close, dismiss, add) against a specific resource (action-plan item) and explicitly points at get_actions as the source of action_id, so it is distinguishable from its siblings 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?

It gives clear operational routing (done vs dismiss vs create) and a mandatory approval workflow before confirm: true, plus where action_id comes from. It stops short of stating when another tool (e.g. update_settings or manage_tracking) would be the better choice, so it is not a full when/when-not guide.

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.