Skip to main content
Glama

List caption signatures

clipember_list_signatures
Read-onlyIdempotent

Show the user's caption signatures (e.g. a call to action or hashtags they end posts with). A signature is added to a post only when you pass its signatureId to clipember_create_post — it is appended to every caption and counts toward each network's caption limit. The one marked auto-add is added automatically only in the person's post editor, never to agent posts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "clipember_list_signatures"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent read, so the description's job is to add domain behavior — and it does: the signature is appended to every caption and counts against each network's caption limit. It also flags a genuine trap: the auto-add flag applies only in the human post editor, never to agent posts, which prevents a wrong assumption about automatic application.

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?

Three tight sentences, front-loaded with the resource definition, then the integration mechanic, then the auto-add caveat. No sentence is redundant and the important warning is placed last for emphasis without burying the purpose.

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?

For a zero-parameter read tool with no output schema, the description covers what the list contains, the key distinguishing attribute (auto-add), and how the result is consumed. It stops short of naming other likely fields (signature name, associated networks), but nothing essential to correct invocation is missing.

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?

The tool takes zero parameters, so there is nothing to disambiguate and the baseline applies. The description still adds useful meaning by naming signatureId as the field the agent will need to reuse in clipember_create_post.

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 resource ("Show the user's caption signatures") and immediately defines the resource with a concrete example ("a call to action or hashtags they end posts with"). An agent can distinguish this from the many other clipember_list_* tools without opening the 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?

The description makes the downstream use case explicit: a signature is applied "only when you pass its signatureId to clipember_create_post," effectively telling the agent this is a prerequisite lookup for post creation. It does not state exclusions or say explicitly to call this before create_post, but the routing is clear.

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