Skip to main content
Glama

This week's SEO and AI search work

seo_set
Read-only

The week's set, picked from the stored search reads (seo_read), the crawl (seo_crawl) and the latest AI visibility run, so the founder does not choose item by item: title rewrites with the most clicks to win back, lifts onto page one, internal links anchored in each target's own best search, a refresh of a page that lost clicks, a new page for a search no page owns, the site fixes, a "what is" page and an AI info page when missing, AI answers lost with their gap, and Bing. Each action says its routine step and what to record (record_action meta), so it is read at 28 and 56 days against the whole site. Also the reads of changes shipped before, and price: what doing the set costs (the research for each page it writes, the lists AI answers cite for a lost answer; the rest is code changes and free). This call is free.

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": "seo_set"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=true. The description adds meaningful context beyond those: the call is free, it includes 'reads of changes shipped before', each action carries its routine step and record_action meta for 28/56-day follow-up, and it exposes a `price` field explaining what doing the set costs. These are useful behavioral details for an agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense paragraph with long run-on sentences and nested parentheticals, so it is poorly front-loaded. While most content is informative, the structure makes it hard to scan and could be significantly improved with a short lead sentence followed by bullets.

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 complex, zero-parameter aggregate tool with no output schema, the description gives a detailed account of what is returned (title rewrites, page-one lifts, internal links, refreshes, new pages, site fixes, AI answers, Bing, prior change reads) plus cost and follow-up recording. It omits the exact return shape, but otherwise provides enough context to understand the call.

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?

The tool takes zero parameters, so the baseline of 4 applies per the scoring rules. The description does not need to explain parameter syntax and appropriately focuses on output content instead.

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?

It clearly identifies the resource as an aggregated weekly action set drawn from seo_read, seo_crawl, and the latest AI visibility run, and enumerates the concrete items included. The verb is implicit rather than a crisp 'returns/generates', and 'set' is jargon that requires reading the whole sentence to decode, but an agent can still distinguish it from sibling data-fetching tools.

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?

The phrase 'so the founder does not choose item by item' implies this tool replaces manual selection, and the data sources suggest it supersedes raw reads. However, there is no explicit statement of when to use this versus seo_read, seo_crawl, plan, or today, nor any exclusions or preconditions.

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