Skip to main content
Glama

Coline

Pinned messages

list_pinned_messages
Read-onlyIdempotent

Lists the messages pinned in a channel or direct message.

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>",
      "type": "<type>",
      "conversationId": "<conversationId>"
    },
    "name": "list_pinned_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
conversationIdYesChannel or direct message id, from list_conversations.

Output Schema

NameRequiredDescriptionDefault
messagesYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already establish a read-only, idempotent, non-destructive, closed-world operation, and the description does not conflict with them. It adds the pinned-in-channel/DM scope, but gives no further behavioral context such as ordering, pagination, limits, or permission requirements.

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?

The single sentence is front-loaded with the action, resource, and scope, with no redundant wording. Its brevity is effective, although additional selection guidance would be useful.

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 simple three-parameter read operation, the required schema, enum, safety annotations, and output schema supply most invocation details. The description is adequate for basic use, but explicit selection guidance and any relevant listing behavior would make it more complete.

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?

With 67% schema coverage, workspace and conversationId are already explained and type has a clear two-value enum. The description expands "dm" to "direct message" and reinforces the conversation scope, but adds little parameter meaning beyond the schema.

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 uses a specific verb and resource—"Lists the messages pinned"—and limits the scope to a channel or direct message. Its pinned-only focus is clear, but it does not explicitly differentiate itself from any sibling message or conversation tool.

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?

The wording implies that the tool should be used when an agent wants pinned messages for a particular conversation. It provides no explicit when/when-not guidance, prerequisites, or alternative for other message-retrieval needs.

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