Skip to main content
Glama

Claude SEO Skills

claudeseoskills__list_ship_nodes

List every node: node_id, title, parent_id, node_type, plus type/description/tags/resource when set. No bodies. This is a flat list of the WHOLE Ship — on a large one it is long and arrives in pages, so pass { cursor } to continue. To navigate rather than enumerate, use claudeseoskills__get_ship_digest.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "claudeseoskills__list_ship_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo

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?

No annotations are provided, so the description carries the behavioral burden, and it does disclose the key traits: bodies are excluded, the list is flat and can be very long on a large Ship, and results arrive in pages. It stops short of stating cursor origin/lifetime or any auth/scope requirements, which would be needed for a 5.

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, each earning its place: field inventory first, exclusion second, paging and alternative last. No filler or restatement of the tool name.

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?

There is no output schema, yet the description covers the return shape by listing the fields and explicitly noting bodies are omitted, plus pagination behavior and the routing alternative. Nothing an agent needs to call this correctly or interpret the result is missing.

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 0% — the schema only declares cursor as a 2048-char string — so the description must compensate, and it does by explaining that the output is paged and cursor is the continuation token. It does not say where the cursor value comes from (presumably the prior response), leaving one small gap.

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?

The description opens with a specific verb and resource ("List every node") and enumerates exactly which fields come back (node_id, title, parent_id, node_type, plus type/description/tags/resource when set), plus a clear exclusion ("No bodies"). It also names the sibling tool for the non-enumerating case, so an agent can distinguish it from get_ship_digest without opening either schema.

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 states the when-to-use condition (enumerate the WHOLE Ship) and the explicit alternative with its selection condition ("To navigate rather than enumerate, use claudeseoskills__get_ship_digest"). Pagination usage is also covered with the concrete "pass { cursor } to continue" instruction.

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.