Skip to main content
Glama

unstar_thread

Remove a star from an Ed Discussion thread to unmark it as important or unfavorite it for future reference.

Instructions

Remove star from a thread

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thread_idYesGlobal thread ID

Implementation Reference

  • The handler function that executes the unstar_thread tool logic by sending a POST request to the API.
    async unstarThread(threadId: number): Promise<void> {
      await this.request("POST", `threads/${threadId}/unstar`);
    }
  • src/index.ts:285-285 (registration)
    The registration of the unstarThread API method within the tool actions mapping.
    unstar: api.unstarThread,
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 behavioral disclosure. It states the action but omits critical operational details such as idempotency (whether calling it on an unstarred thread errors or succeeds silently), authentication 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?

The description is extremely brief (5 words) with no redundant or wasted language. However, the brevity leaves significant informational gaps that should have been included given the lack of annotations.

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 single-parameter mutation tool with no output schema and no annotations, the description is insufficient. It lacks behavioral constraints, error conditions, or domain context necessary for reliable agent invocation.

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 100% with 'Global thread ID' documented. The description adds no parameter-specific context, but this meets the baseline expectation when schema coverage is high.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description expands 'unstar' to 'Remove star from a thread', providing a clear verb and resource. However, it does not explain what 'starring' represents in this domain (e.g., bookmarking vs. liking) or distinguish this tool from its inverse sibling 'star_thread'.

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?

The description provides no guidance on when to use this tool versus alternatives. It fails to mention prerequisites (e.g., whether the thread must currently be starred) or the relationship to 'star_thread'.

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