Skip to main content
Glama

send_back_post

Returns a link the user opens to send a post back to its author with a note saying what needs to change (request changes), the opposite verdict to approve_post, on a post the user is reviewing. Like approving, the verdict is the user's to give: this returns a link they open to read the copy and their note and press Send back themselves. The note reaches the author verbatim, so write it as the user said 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": {
      "post_id": "<post_id>",
      "note": "<note>"
    },
    "name": "send_back_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYesRequired. What needs to change, in the user's own words.
post_idYesThe id of the post to send back
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: the tool does not deliver anything itself, it returns a link the user must open and confirm, and the note reaches the author verbatim. That last point materially changes how an agent should phrase the note, and none of it is derivable from readOnlyHint=false / 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?

The key fact, that this returns a link rather than sending anything, is front-loaded in the first clause. The second sentence is long and mildly repetitive of the first ('the verdict is the user's to give' restates the human-confirmation point), but no sentence is disposable.

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?

Although there is no output schema, the description explains exactly what comes back (a link the user opens) and what the user sees at that step, which fills the main gap for a three-parameter mutation-adjacent tool. Missing only minor details such as link lifetime or whether the post leaves the review queue immediately.

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 baseline is 3, but the description earns a bump by explaining that the note is transmitted to the author word-for-word, which implies an instruction to preserve the user's wording rather than paraphrase. It adds no guidance on the optional workspace parameter, which the schema already covers.

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?

Names a specific verb and resource ('Returns a link... to send a post back to its author') plus the review verdict it represents, and explicitly frames it as 'the opposite verdict to approve_post'. An agent can distinguish it from approve_post and from comment_on_post 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?

Context is clear: use it on 'a post the user is reviewing' when the desired verdict is request changes rather than approval, with approve_post named as the counterpart. It stops short of stating exclusions (e.g. own drafts, already-published posts, or what to do if the post was already sent back), so it is slightly below fully explicit routing guidance.

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