Skip to main content
Glama

Add page link

page_link_add

Add a HTTPS link to Your page (maximum 30). Known URL shorteners are refused. 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": {
      "link": "<link>"
    },
    "name": "page_link_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYes
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
Behavior5/5

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

Annotations only declare the generic mutation profile (readOnlyHint false, destructiveHint false, non-idempotent). The description adds real behavior: a 30-link ceiling, shortener rejection, the draft-versus-published-page workflow, the human-approval gate for confirm_publish, and the required API key scope 'draft'.

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?

Four short sentences ordered purpose → validation limits → publish workflow → auth scope. No filler, and the most decision-relevant facts come first.

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 nested-object mutation with no output schema, the description covers the risky parts well: the draft/approval gate, the count limit, URL validation, and the required scope. The remaining gap is the scheduling and display fields inside the link object, which an agent must infer from the schema alone.

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 50%: confirm_publish is already documented in the schema, so the description's restatement of it adds little. It does clarify that the URL must be HTTPS and that shorteners are rejected, but the nested link fields (enabled, position, starts_at, ends_at, thumbnail_url) remain unexplained in both places.

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: 'Add a HTTPS link to Your page', plus a hard cap of 30. The verb 'add' naturally separates it from the page_link_update and page_link_remove siblings, though no sibling is named explicitly.

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 concrete conditions for use: known URL shorteners are refused, a 30-link maximum applies, and on a published page the change waits as a draft until confirm_publish: true is passed after explicit approval. It stops short of naming page_link_update as the alternative for editing an existing link.

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