Skip to main content
Glama

Approve marketing drafts

gtm_approve_content
Idempotent

Approve one or more of your PromptUI drafts so they can be published or scheduled. Does not publish or schedule by itself. Each draft gets the same checks as Approve in the app; a draft that is not ready says why.

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": {
      "contentIds": "<contentIds>"
    },
    "name": "gtm_approve_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
_confirmedNoSet to true only after the user has explicitly approved this exact write or credit-spending action.
contentIdsYesThe draft ids to approve (1 to 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is covered; the description adds real value by clarifying that approval is a prerequisite gate rather than a publish action, that each draft is validated with the same checks as the in-app flow, and that rejected drafts return a reason. It omits partial-success semantics when some ids fail and does not surface the _confirmed gate in prose.

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 short sentences with the action and its scope front-loaded, followed by the critical limitation and the validation behavior. Nothing is padded; the 'same checks as Approve in the app' clause earns its place by explaining why a call can fail per draft.

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 two-parameter mutation with full schema coverage and a clear annotation set, the description covers action, scope, limitation, and failure reporting. It stops short of describing mixed-result behavior across the id array, which is the one gap an agent could stumble on.

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 100%, so both contentIds and _confirmed are already documented in the input schema, including the 1-to-20 bound and the confirmation rule. The description only echoes 'one or more' drafts and adds no syntax, batching, or ordering detail beyond the schema, so the baseline 3 applies.

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 ('Approve one or more of your PromptUI drafts') and immediately scopes the effect ('so they can be published or scheduled'), which separates it from gtm_publish_content. An agent can distinguish the state-transition step from the publication step without opening any 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?

Gives a clear when-to-use context plus an explicit exclusion: 'Does not publish or schedule by itself,' which routes the agent to gtm_publish_content for the follow-up step. It does not name that sibling directly nor state preconditions such as unapproved-only drafts, so it falls short of a full when/when-not map.

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