PostRite

Resend an approval request

resend_approval

Re-send the external approval email for a post to its approver(s) — works while it is PENDING_APPROVAL, or after the link expired (mints a fresh link). To list posts awaiting approval, use list_posts with status PENDING_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": {
      "postId": "<postId>"
    },
    "name": "resend_approval"
  }
}

Input Schema

Name	Required	Description	Default
`postId`	Yes	The post ID (from list_posts)
`organizationId`	No	Organization to act in — an id from list_organizations. Required when this connection was authorized for more than one organization; omit it when there is only one.

Output Schema

Name	Required	Description	Default
`post`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The annotations already flag a non-read-only, open-world, non-idempotent, non-destructive operation, so the external-email part is partly covered. The description still adds real value by saying that a call mints a fresh link (which explains why repeats are not idempotent) and by tying the tool to a specific post state. It does not say whether the previously issued link stops working or whether there are send-rate limits, which keeps it below a 5.

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, with the action and its preconditions front-loaded and the alternative tool named last. Every clause carries information: scope, state precondition, expired-link behavior, and routing.

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?

Because an output schema exists, return values do not need to be explained, and the annotations cover the safety profile. What the description covers — preconditions and the fresh-link behavior — is enough for correct invocation. Only minor gaps remain, such as whether the old link is invalidated and any limit on repeated sends.

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%: postId and organizationId are both documented in the schema, including the multi-org rule for organizationId. The description adds no syntax, format, or edge-case detail for either parameter, so the schema is doing all the work and a 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?

The description gives a specific verb and resource: re-send the external approval email for a post to its approver(s). It also distinguishes this tool from list_posts, which it names as the way to enumerate candidates, so the agent can separate it from siblings like list_posts or get_approval_analytics without needing their schemas.

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?

It states the exact conditions under which the tool applies (post is PENDING_APPROVAL, or the approval link has expired) and names the alternative for the adjacent need (list_posts with status PENDING_APPROVAL). This is explicit when-to-use plus routing, not just an implied context.

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

All PostRite tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?