Skip to main content
Glama
Sign In

OrgLines

by com.orglines
OverviewDiscussionsAdmin

SEO: Estimate research cost

seo_estimate
Read-only

Price an SEO research before starting it, from the same inputs seo_start_research takes: AI credits charged at start, the upper bound for the full research stage by stage, the workspace's credit balance and whether it can start now. Pass project_id instead to price a re-run of an existing project. Nothing is created or charged. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
cityNoOptional target city (key or name, e.g. «Київ»). Empty = whole country; queries naming another city are kept outside the plan.
languagesNoQuery languages to collect, site language first, e.g. ["uk","ru"]. Non-site queries are translated and clustered together with the rest.
project_idNoSEO project id as returned by seo_list_projects.
language_codeNoThe SITE language (default uk). Proposals are written in it.
location_codeNoMarket: 2804 Ukraine (default), 2276 Germany.
seed_keywordsNoStarting phrases describing the business, e.g. «шиномонтаж».
budget_keywordsNoCore keywords to collect (default 3000). Drives the price.
serp_verify_top_nNoHow many top keywords get their Google top-10 checked (default 100).

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?

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'Nothing is created or charged', which matters for an agent deciding whether a pre-check is safe. It also discloses the return payload (credits charged at start, stage-by-stage upper bound, balance, readiness) despite no output schema existing, though it does not say how precise the estimate is beyond 'upper bound'.

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?

Two tight sentences: the first gives purpose, input contract and return contents; the second covers the alternate mode and the no-side-effect guarantee. Nothing is repeated from the schema and the safety statement is front-loaded at the end where it closes the decision.

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 compensates by enumerating what the estimate returns (start cost, stage-by-stage ceiling, balance, readiness), and all eight parameters are documented in the schema. For a read-only pricing tool this is enough to call it correctly and interpret the result.

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

Parameters3/5

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

Schema coverage is 100% and schema descriptions already explain budget_keywords drives price and serp_verify_top_n controls verification depth. The description only adds the meta-point that inputs mirror seo_start_research and that project_id substitutes for seed_keywords, which is useful routing but no per-parameter detail beyond the schema.

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?

States a specific verb and resource ('Price an SEO research') and pins the scope by tying its inputs to seo_start_research, so an agent can tell it apart from the sibling that actually launches research. The re-run variant via project_id is called out explicitly.

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?

Explicitly frames usage as pricing 'before starting it', names the sibling whose inputs it mirrors, and gives the alternative path (pass project_id instead of seed_keywords to price a re-run). No inference is needed to pick between estimating and starting.

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

All OrgLines 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