Skip to main content
Glama

unendorse_thread

Remove endorsement from a thread in Ed Discussion to manage thread status and visibility.

Instructions

Remove endorsement from a thread

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thread_idYesGlobal thread ID

Implementation Reference

  • The API method that sends the request to the backend to unendorse a thread.
    async unendorseThread(threadId: number): Promise<void> {
      await this.request("POST", `threads/${threadId}/unendorse`);
    }
  • src/index.ts:300-312 (registration)
    Dynamic registration of thread actions, including unendorse_thread, which uses threadActions[action] to call the corresponding API method.
    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?

No annotations are provided, so the description carries the full burden. While 'Remove' implies a mutative operation, the description fails to disclose error conditions (e.g., thread not found), idempotency, authorization requirements, or side effects.

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?

Extremely brief at only four words. While efficient and without redundancy, it borders on under-specification for a mutative operation; a single additional sentence explaining behavior or prerequisites would improve utility.

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

Completeness3/5

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

Given the tool's simplicity (single ID parameter, no output schema), the description is minimally viable but leaves gaps. Without annotations to indicate safety or destructiveness, the description should have elaborated on behavioral outcomes.

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 input schema has 100% description coverage ('Global thread ID'), so the baseline is 3. The description adds no additional parameter semantics, but none are needed given the complete schema documentation.

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?

States a clear verb ('Remove') and resource ('endorsement from a thread'), accurately describing the operation. However, it does not explicitly differentiate from siblings like 'unendorse_comment' or explain the relationship to 'endorse_thread' within the text.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., 'endorse_thread'), nor does it mention prerequisites such as whether the thread must currently be endorsed or what happens if called repeatedly.

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