Skip to main content
Glama

set_pinned_items

DestructiveIdempotent

Pin up to 3 "Top Picks" shown first on the collection share page. Example: collection_id, item_ids=["", ""].

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": {
      "collection_id": "<collection_id>",
      "item_ids": "<item_ids>"
    },
    "name": "set_pinned_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoWhy, for the change history
item_idsYesItems in display order
collection_idYesCollection ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / collection_id / description
      Previous value: -"The collection ID"New value: +"Collection ID"
    • changedInput schema / properties / item_ids / description
      Previous value: -"Items to pin, in display order (1st = top)"New value: +"Items in display order"
    • addedInput schema / properties / item_ids / maxItems
      Added value: +3
    • addedInput schema / properties / item_ids / minItems
      Added value: +1
    • changedInput schema / properties / reason / description
      Previous value: -"Why this change was made (shown to user in change history)"New value: +"Why, for the change history"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety bar is lower, but the description never explains the destructiveness — crucially whether this call REPLACES the existing pinned set (removing prior pins) or adds to it. For a tool flagged destructive, that replacement semantics is the single most decision-relevant fact and it is absent. The description does add useful context on the display effect ('shown first on the collection share page').

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?

Two sentences, front-loaded with the effect, and the example is compact. The example largely duplicates what the schema already conveys about required fields, so it is marginally wasteful, but nothing is padded or buried.

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

Completeness4/5

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

No output schema exists and the tool is a simple 3-parameter mutation, so the description need not cover return values. What remains missing is behavioral rather than structural: the replace-vs-append semantics and any constraint on which items are eligible to be pinned.

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%, so all three parameters (collection_id, item_ids, reason) are already documented, including 'Items in display order' and maxItems=3. The description restates the 3-item cap and the display prominence but adds no new syntax, format, or ordering semantics beyond the schema. Baseline 3 applies.

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+resource: pinning items as 'Top Picks' displayed first on a collection's share page. That is clearly distinguishable from every sibling (add_item, update_collection, link_items), none of which touch share-page pinning. It stops short of 5 only because it doesn't name update_collection as the non-pinning alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Top Picks' framing implies when this applies, and the example shows a concrete call shape, but there is no explicit when-to-use vs. when-not guidance and no mention of prerequisites (e.g., whether items must already be in the collection). Usage must be inferred from the goal statement.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources