Skip to main content
Glama

Coline

Pin message

pin_message

Pins a message to its conversation for everyone, or unpins it if it's pinned.

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": {
      "workspace": "<workspace>",
      "messageId": "<messageId>"
    },
    "name": "pin_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
pinnedNotrue pins it, false unpins it; leave it out to toggle.
messageIdYesMessage id from read_conversation.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
conversationIdNoFrom list_conversations.

Output Schema

NameRequiredDescriptionDefault
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already state readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false. The description adds one genuinely useful behavioral fact - the pin is visible to everyone in the conversation, not just the caller - which is not in the schema or annotations. However, it omits permission requirements, notification side effects, and how the toggle interacts with repeated calls, so it goes only modestly beyond the structured data.

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?

One efficient sentence with the action front-loaded and no filler. The trailing 'or unpins it if it's pinned' clause is compact but slightly ambiguous about whether unpinning happens automatically or only when requested.

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?

With an output schema present, the description needn't explain return values, and annotations carry the safety profile, so the remaining burden is light. It covers the core action and visibility scope; the main gaps are permission prerequisites and the exact toggle semantics, which the schema largely covers anyway.

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 80%, and the schema itself explains the `pinned` boolean more precisely than the description does ('true pins, false unpins, leave it out to toggle'). The description's 'unpins it if it's pinned' gestures at the `pinned` parameter but adds no clarity about syntax, defaults, or the type/conversationId parameters, so baseline 3 applies.

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?

Uses a specific verb (pins) and resource (a message) and states scope ('to its conversation for everyone'), so the action is unambiguous. It does not differentiate itself from nearby siblings such as save_message or set_message_priority, leaving the agent to infer which one to reach for.

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 framing, no exclusion of alternatives, and no prerequisite context (e.g., what permissions are needed to pin 'for everyone'). The only usage hint is the conditional 'unpins it if it's pinned', which is about mechanics rather than tool selection.

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