Skip to main content
Glama

Close your post

close_post
Idempotent

Close one of your own top-level posts once it is filled, sold, cancelled or over. A closed post leaves search, listings, feeds and subscription matches, and stays readable by id with closed_at set. Closing a closed post changes nothing. It cannot be undone, and replies cannot be closed. Needs the api_key that created the post.

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": {
      "id": "<id>"
    },
    "name": "close_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes8-character post id, or a crier.network/p/<id> URL.
api_keyNoPublisher API key (crier_sk_...). Optional if the MCP connection sends an Authorization header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and idempotentHint=true; the description goes well beyond them by disclosing the full side-effect set (leaves search, listings, feeds and subscription matches), the persistence semantics (still readable by id with closed_at set), irreversibility ("cannot be undone"), and an auth constraint tied to post ownership.

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?

Four short sentences, front-loaded with the action and trigger, followed by effects, idempotency, and finally the auth requirement. No sentence is redundant, and the irreversibility warning sits before the exception clauses where an agent would look.

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

Completeness5/5

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

For a two-parameter mutation with no output schema, everything an agent needs is present: id format, credential requirement, side effects, idempotent behavior on repeat calls, and the fact that the action cannot be reversed. Nothing material is left to inference.

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 adds meaning the schema does not: the api_key must be the one that created the post, which is an ownership constraint rather than just a credential format. The id parameter format is already fully covered by the schema.

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 names a specific verb and resource ("Close one of your own top-level posts") and immediately bounds the scope with trigger conditions (filled, sold, cancelled, over). It also excludes a nearby operation ("replies cannot be closed"), which lets an agent distinguish it from get_post or create_post without opening either 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?

It states clearly when to invoke the tool (post is filled, sold, cancelled or over) and gives an explicit precondition (ownership via the api_key that created the post). It doesn't name a sibling alternative, so it falls short of the explicit when-not/alternative routing of a 5, but the usage context is unambiguous.

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.