Skip to main content
Glama

Claude SEO Skills

claudeseoskills__read_node

Read one node's full markdown body + frontmatter by node_id. Response includes outbound_links[] (resolved graph edges) unless with_links:false, plus source attribution. Pass heading (e.g. "Tactics") to get ONLY that markdown section — a few hundred chars instead of the whole body; every heading read, hit or miss, carries the node's headings list, and a miss is heading_not_found — so a guessed heading is cheap (heading "" just lists the headings). A heading read is partial — never write it back as a node's content; re-read without heading first. A long body is returned one page at a time — when the response says truncated, call again with { cursor } to continue it.

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": {
      "node_id": "<node_id>"
    },
    "name": "claudeseoskills__read_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
headingNo
node_idYes
with_linksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the response payload (outbound_links plus source attribution, suppressible via with_links:false), pagination semantics tied to a truncation signal, the cost profile of heading reads, and the heading_not_found error shape. It stops short of stating behavior for a missing/invalid node_id or any permission requirements, which is the remaining gap.

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 purpose and return shape are front-loaded, and every sentence carries operative information rather than filler. It is dense with em-dashes and nested parentheticals, so a reader must work harder than necessary, but nothing is truly redundant.

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

Completeness5/5

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

For a four-parameter read tool with no output schema and no annotations, the description covers return contents, the with_links toggle, partial-read hazards, pagination continuation, and one error mode — enough for an agent to call it correctly on the first attempt in the common cases.

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

Parameters5/5

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

Schema description coverage is 0% with four parameters, so the description must compensate and does: node_id is the lookup key, heading selects a section (with an example, an empty-string special case, and a defined miss behavior), with_links:false drops the links array, and cursor continues a truncated body. Each parameter's meaning goes well beyond its name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Read one node's full markdown body + frontmatter by node_id" names a specific verb (read), a bounded resource (one node), and the key selector (node_id), which cleanly separates it from the sibling list/search tools that operate over many nodes.

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

Usage Guidelines5/5

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

It gives explicit conditional guidance: pass heading to get only a section, use heading "" to list headings, re-read without heading before writing back, and call again with { cursor } when the response says truncated. It also warns against a specific misuse (writing a partial heading read back as node content).

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.