Skip to main content
Glama

content-reject

Destructive

Reject content

Reject a content item with the built-in reject action, and resolve it in the review queue.

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": {
      "request": "<request>"
    },
    "name": "content-reject"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds one genuinely new behavioral fact — that the action also resolves the queue item — but is silent on irreversibility, webhook emission, or what happens to already-rejected content.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The second sentence is dense and front-loaded, but the leading "Reject content" line merely repeats the title and the tool name and earns nothing. Two sentences total, one of which is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive, non-idempotent mutation with a deeply nested body and no output schema, so the description carries real weight — yet it never says whether the rejection is reversible, whether rejected content is removed or merely flagged, or whether a reason is required for the webhook. For a destructive operation that is a meaningful omission.

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?

The measured top-level coverage is 0% (the single `request` wrapper is undocumented), which normally puts the burden on the description, and the description says nothing about id, reason, moderator, queueId, projectId, or the casebook flag. Mitigating this: the nested schema properties are themselves well described, so the practical meaning of each field is still discoverable — hence 3 rather than lower.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Reject a content item") and adds the outcome ("resolve it in the review queue"), which is more than a restatement of the name. It does not distinguish itself from the closest sibling, content-allow, or from queue-items-resolve, so an agent still has to infer the boundary.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no prerequisites, and no mention of alternatives such as content-allow for the opposite decision or queue-items-resolve for generic queue handling. Usage is only implied by the verb itself.

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