Skip to main content
Glama

Send a revised post back for approval

resubmit_post

After a reviewer clicked "Ask for changes" (get_post: approval.state "changes_requested", approval.feedback says what to fix), revise the post with update_post, then call this to send it back for approval. It returns to its earlier time if still ahead, else the next queue slot after approval.

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>"
    },
    "name": "resubmit_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
replyNoOptional. What you changed, shown to the reviewer.
post_idYesThe post ID (UUID).
scheduled_forNoOptional. New time, ISO 8601 with offset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only say non-destructive and non-idempotent; the description adds real behavioral context by explaining what happens to scheduling: it restores the earlier time if still ahead, otherwise it lands in the next queue slot after approval. It does not say what happens if the post is not in changes_requested state, nor whether prior feedback is cleared.

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?

A single tight sentence chain with the precondition front-loaded and the state name quoted for exact matching. The nested parenthetical is dense but every clause carries operational information; nothing is filler.

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?

Covers the workflow entry condition, the required prior tool, the scheduling side effect, and the meaning of the optional reply. For a 3-parameter mutation with no output schema, the only notable gap is failure behavior when the post is not in changes_requested state.

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 all three parameters (post_id, reply, scheduled_for) are already documented. The description adds no syntax or format detail beyond that — the scheduling sentence implies what scheduled_for affects but does not restate the field's rules. Baseline 3 is appropriate.

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 outcome ('send a revised post back for approval') and anchors it to a precise workflow state (approval.state "changes_requested"). It is clearly distinguishable from update_post (which edits) and approve_queued_post (which approves someone else's submission).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition (a reviewer clicked "Ask for changes"), the preceding step (revise with update_post), and then the trigger to call this tool. An agent cannot confuse the ordering or skip the required step.

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