Skip to main content
Glama
Sign In

mowteng

by app.mowteng
OverviewDiscussionsAdmin

List the day's SEO tasks

todo_list
Read-only

A site's SEO tasks for the day, computed live from its sitemaps, Search Console, Bing and Yandex; nothing is stored, so the same day gives the same list. Tasks: pages changed since yesterday to submit via IndexNow (Bing and Yandex submissions as alternatives), sitemaps to resubmit to Google, sitemap errors, and in the weekly view pages Bing has not crawled since they changed. Each item names the tool call that does it. Engines that are not connected are skipped and listed.

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": {
      "site": "<site>"
    },
    "name": "todo_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueNotoday: what to do now. tomorrow: changed pages past today's 200-URL cap. week: sitemap health and pages changed this week that engines have not picked up. Defaults to today.today
siteYesSearch Console property exactly as gsc_list_sites returns it: "https://example.com/" or "sc-domain:example.com"

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, it discloses that nothing is stored and the same day yields the same list (determinism), and that engines that are not connected are skipped and surfaced in the output. It does not mention auth requirements or whether the live computation is slow or rate-limited, so it stops short of full behavioral coverage.

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 scope statement is front-loaded and every clause carries information; there is no filler. The first sentence is a dense run-on with semicolons, which costs a little readability but not correctness.

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?

With no output schema, the description carries the return-value burden and does so: it lists the task categories, says each item names the tool call that performs it, and notes unconnected engines appear as a listed gap. An agent can act on the result without further documentation.

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 100%, so the baseline is 3, but the description adds real meaning by enumerating what each view actually surfaces (IndexNow candidates, Google sitemap resubmits, sitemap errors, weekly uncrawled pages). That reinforces and slightly extends the enum documentation rather than merely restating it.

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 states a specific verb and resource ('A site's SEO tasks for the day, computed live from its sitemaps, Search Console, Bing and Yandex') and positions the tool as an aggregator whose items name the sibling tool calls that perform the work. That makes it clearly distinguishable from the per-engine siblings like gsc_list_sitemaps or bing_crawl_issues.

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 clear context for when this is the right entry point (a computed daily worklist) and explains the three view modes' intent, plus the note that unconnected engines are skipped and listed. It stops short of an explicit 'use this before calling the individual submit tools' directive or any when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mowteng toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources