Skip to main content
Glama

Reorder page links

page_links_reorder
Idempotent

Replace link ordering. Include every workspace link ID exactly once. On a published page the change is saved as a draft and the public page keeps its approved version until the person approves publishing; then pass confirm_publish: true. Requires API key scope: draft.

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": {
      "ids": "<ids>"
    },
    "name": "page_links_reorder"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
confirm_publishNotrue only after the person explicitly approved publishing; without it, changes to a published page wait as a draft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare this is a non-read-only, idempotent, non-destructive mutation; the description goes beyond that by explaining the draft/approval lifecycle on published pages and the required API key scope ('draft'), which is genuinely non-obvious. It stops short of saying what happens when the supplied ID list is incomplete or exceeds limits, leaving error behavior implicit.

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?

Three short sentences, each carrying distinct load: the action, the payload constraint, then the publish-approval behavior and scope. The key constraint and the confirm_publish condition are front-loaded with no filler.

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?

For a two-parameter mutation with no output schema, the description covers the action, the exhaustive-list requirement, the draft-publication consequence, and the auth scope. Remaining gaps are minor but real: the meaning of array position as ordering and the maximum list size are left to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: confirm_publish is documented in the schema, but ids is only typed, so the description must compensate and does by specifying that IDs must be workspace link IDs, exhaustive, and non-duplicated. It does not mention that the array order defines the resulting order nor the 30-item cap, which remain for the agent to infer.

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?

The description opens with a specific verb and resource, 'Replace link ordering', and immediately clarifies the payload semantics ('Include every workspace link ID exactly once'), which separates it from an additive link tool without needing the schema. It does not explicitly name a sibling as an alternative, so it stops short of full differentiation.

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

Usage Guidelines4/5

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

It gives a clear operational rule (send the complete set of workspace link IDs exactly once) and a conditional instruction for the publish path ('then pass confirm_publish: true'), which tells the agent when that parameter applies. It does not state when to prefer a different link tool or what to do if the ordering is unchanged, so there is no explicit exclusion guidance.

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