Skip to main content
Glama
fgasparetto
by fgasparetto

unpin_article

Unpin an article by its ID to remove it from the top of the article list.

Instructions

Remove pin from an article (remove from TOP).

Args: article_id: ID of the article to unpin

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
article_idYes
Behavior2/5

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

With no annotations provided, the description only gives minimal behavioral context ('remove from TOP'). It does not disclose side effects, error conditions, or the effect on article ordering beyond removing the pin.

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 description is extremely concise with no extraneous information. It is front-loaded with the primary action and includes a parameter description in a clear format.

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 simple mutating tool, the description lacks crucial context: error scenarios (e.g., article not pinned), return value (if any), and any changes to the state beyond removing the pin. No output schema is present, so the description should cover the outcome.

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 description adds some meaning to the lone parameter by stating 'ID of the article to unpin', which clarifies its role beyond the schema's type definition. However, it does not explain how to obtain the ID or any constraints.

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

Purpose5/5

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

The description clearly states the verb 'Remove pin' and the resource 'article', and distinguishes it from the sibling tool 'pin_article' by indicating the reverse operation.

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 on when to use this tool versus alternatives, no prerequisites or conditions (e.g., article must be pinned first).

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/fgasparetto/chipsnews-mcp'

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