Skip to main content
Glama

authors-unblock

Unblock author

Unblock a blocked or suspended author with the built-in unblock action, so they can post new content again.

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": "authors-unblock"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the post-restoration effect; it does not explain the webhook event fired, whether calling it twice on a non-blocked author errors (relevant given idempotentHint=false), or what permissions/project scope are required. Modest value beyond the annotations, not rich context.

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?

Two short sentences, front-loaded with the action and followed by the outcome. The opening line duplicates the tool title verbatim, which is mild waste, but nothing else is padded.

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 state-changing, open-world, non-idempotent operation with a nested parameter object and no output schema, yet the description covers none of the operational context: what is restored (author status only, or their held content), what a failure looks like, or what the reason/webhook side effect is. For this complexity level the definition is thin.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description says nothing about any parameter — not the author id, not the optional reason, not project scoping. The context signal reports 0% schema description coverage, and the description makes no attempt to compensate for the nested request/body/id wrapper or to explain that 'reason' is persisted and echoed in the webhook event.

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?

The description gives a specific verb+resource ('Unblock a blocked or suspended author') and states the outcome ('so they can post new content again'), which is more than a restatement of the name. It implies but never names the counterpart tools (authors-block, authors-suspend), so sibling differentiation is left to the agent's inference.

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

Usage Guidelines3/5

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

Usage is implied by the precondition 'blocked or suspended author' — the agent can infer this applies only to currently restricted authors. There is no explicit when-not guidance (e.g. what happens if the author is not blocked), no mention of the block-vs-suspend distinction, and no pointer to authors-block/authors-suspend as the inverse operations.

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