Skip to main content
Glama

pin_thread

Pin a discussion thread to the top of the forum to ensure it remains visible and accessible to all users.

Instructions

Pin a thread to the top

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thread_idYesGlobal thread ID

Implementation Reference

  • The actual implementation of the pin thread request.
    async pinThread(threadId: number): Promise<void> {
      await this.request("POST", `threads/${threadId}/pin`);
    }
  • src/index.ts:300-312 (registration)
    The MCP tool registration logic that dynamically creates the 'pin_thread' tool.
    server.tool(
      `${action}_thread`,
      threadActionDescs[action],
      { thread_id: z.number().describe("Global thread ID") },
      async ({ thread_id }) => {
        try {
          await threadActions[action].call(api, thread_id);
          return msg(`Thread ${thread_id} ${action}ed successfully.`);
        } catch (err) {
          return fail(err);
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosure but fails to address critical behavioral traits: whether multiple threads can be simultaneously pinned, what happens to previously pinned threads, if the operation is idempotent, or what authorization is required. 'Pin' implies a mutation but specifics are absent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief (4 words) and efficiently structured, but given the lack of annotations and output schema, it is underspecified rather than appropriately concise. It fails to provide the necessary behavioral context that would justify its brevity.

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?

For a mutation tool with no output schema and no annotations, the description is incomplete. It omits: the scope of 'top' (forum, category, global), return value information, error conditions (e.g., thread not found), and side effects on other threads' pinned status.

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?

The schema has 100% description coverage ('Global thread ID'), establishing a baseline of 3. The description itself adds no parameter-specific context (e.g., where to find this ID, format requirements), but the schema is sufficiently self-documenting for this single-parameter tool.

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 provides a clear verb ('Pin') and resource ('thread'), and the phrase 'to the top' distinguishes it from sibling tools like star_thread (marking as favorite) and lock_thread (restricting access). However, it lacks domain context (e.g., 'top of the forum/feed') that would make it a 5.

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?

No guidance provided on when to use this tool versus alternatives like star_thread, or prerequisites such as required permissions. The existence of unpin_thread as a sibling suggests a reversible state, but the description doesn't clarify the relationship or when to prefer pinning over other actions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rob-9/edstem-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server