Skip to main content
Glama

Claude SEO Skills

claudeseoskills__search_nodes

Search nodes by text, node_type, and/or semantic type. Token-AND across title + description + tags. Primary retrieval path — use it before reading bodies. Results are ranked best match first — score on each row is the match strength (title hits count double). Page 1 is the top of the ranking. A one-word query can match hundreds of rows — put two or more terms in query so the top rows are the answer, not a dump. Terms are AND-ed: if two return nothing, drop one. Reports total_matches; when more matches exist than fit in one response, narrow the query or pass { cursor } for the next page (a cursor is only valid for the query that produced it).

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__search_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
queryNo
cursorNo
node_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/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 behavioral burden and does most of it: it discloses the token-AND matching model, that ranking is best-match-first with title hits weighted double, that a score is returned per row, that total_matches is reported, and that a cursor is only valid for the query that produced it. It does not state read-only/safety semantics or what fields each returned node row contains, which are the remaining gaps.

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?

It is front-loaded with purpose and every clause adds operational information rather than restating the name. It is dense and unbroken prose with no visual separation between matching semantics, ranking, and pagination, which makes it slightly harder to scan than it needs to be.

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 4-parameter, zero-annotation, no-output-schema tool, the description covers matching semantics, ranking, result-count reporting, and pagination — nearly everything needed to call it correctly. The residual gap is that the shape of a returned node row and the node_type vs. type distinction are left unstated.

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 description coverage is 0%, so the description must define all four parameters, and it substantively does for query (terms AND-ed, multi-term advice, 1000-char cap implied by schema) and cursor (next-page token, scoped to its originating query). node_type and semantic type are named but the distinction between the two taxonomies is never explained, leaving the most ambiguous pair under-specified.

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 opening sentence names a specific verb (search) and resource (nodes) and lists the three matchable dimensions: text, node_type, and semantic type. It also positions itself against the sibling that reads full content with 'Primary retrieval path — use it before reading bodies', so an agent can separate it from read_node 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 gives explicit ordering guidance ('use it before reading bodies'), a concrete query-construction rule (two or more terms, because one word can match hundreds of rows), a fallback when AND-ing fails ('drop one'), and pagination guidance (narrow the query or pass cursor). When-to-use, how-to-use, and what to do on failure are all covered.

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.