Skip to main content
Glama

unpin_tag

Removes a tag from the pinned list in flomo, restoring its normal position in the tag list.

Instructions

取消置顶标签

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": {
      "tag": "<tag>"
    },
    "name": "unpin_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYes标签名

Output Schema

NameRequiredDescriptionDefault
tagYes
pinnedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
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 behavioral burden. It implies a state mutation (removing a pin) but says nothing about whether the tag must currently be pinned, whether the call is idempotent, what error occurs if it is not pinned, or whether pinned-tag ordering elsewhere is affected.

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 a single front-loaded phrase with zero filler or redundancy. Its brevity is efficient, though it borders on under-specification rather than true conciseness.

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?

The output schema means return values need not be explained, and there is only one simple parameter. However, for a mutation tool with no annotations at all, the definition provides no behavioral context, so an agent cannot predict error conditions or side effects before invoking it.

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?

There is a single required parameter whose schema entry is fully described ("标签名"), so coverage is 100%. The description adds no additional meaning such as whether the tag is matched by name or ID, or whether an unknown tag name errors — baseline 3 applies when the schema already does the work.

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 specific verb (unpin/remove pin) and a specific resource (tag), so the agent knows exactly what operation is performed. It does not explicitly distinguish itself from the sibling pin_tag or explain the resulting state, so it falls short of the sibling-differentiation bar for 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?

The description contains no when-to-use guidance, no prerequisites, and no mention of the counterpart pin_tag operation. The usage is only inferable from the tool name itself, which is the definition of implied rather than stated guidance.

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