Skip to main content
Glama

Update page link

page_link_update
Idempotent

Update a workspace page link by ID. Omitted fields stay unchanged. 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": {
      "id": "<id>",
      "updates": "<updates>"
    },
    "name": "page_link_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
updatesYes
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/5.0
Behavior5/5

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

The annotations only declare the generic profile (not read-only, not destructive, idempotent), while the description adds the crucial mutation semantics: published pages persist changes as a draft, the public page keeps its approved version until approval, and confirm_publish is the approval gate. It also discloses the required API key scope ('draft'), which the annotations do not.

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 tight sentences lead with the action, then the patch semantics, then the publish workflow, and close with the scope requirement. Every clause carries distinct information and nothing is repeated from the schema or annotations.

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 three-parameter mutation tool with a nested update object and no output schema, the description supplies the semantics an agent most needs: partial-update behavior, the draft/approval workflow, and auth scope. The chief omission is any guidance on the nested field meanings or on failure behavior.

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?

With schema coverage at 33%, the description does useful work: it explains that 'updates' is a partial patch where omitted fields stay unchanged, and it explains the conditional meaning of confirm_publish. However, the seven nested fields (url, label, enabled, starts_at, ends_at, position, thumbnail_url) receive no treatment in either place, leaving a real gap.

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 uses a precise verb and resource ('Update a workspace page link by ID'), which cleanly separates it from page_link_add and page_link_remove. It stops short of naming a sibling to route against, but the purpose is unambiguous.

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?

Usage is implied by 'Update ... by ID' and 'Omitted fields stay unchanged', which signals a partial-update tool. It never says when to pick this versus page_link_add or page_update, nor does it state preconditions for calling it beyond the scope requirement.

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