Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Start Job Tool

adataforseo.start_job

Starts background SEO data jobs after an estimate review, respects spend and monthly caps, and routes unknown or high-cost jobs for approval.

Instructions

Starts background work that can cost money. Review adataforseo.estimate with the same kind and options first. Requires adataforseo_spend and respects job and monthly caps; unknown or high estimates wait for approval in the module. Returns the job uuid, status, estimate and spent amount.

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": {
      "kind": "<kind>"
    },
    "name": "adataforseo.start_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesJob kind
optionsNoJob options: crawl_pages, javascript, priority, depth, recheck, keywords; custom jobs also accept endpoint, tasks and variant. Budgets and permissions cannot be overridden.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.4

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the single readOnlyHint=false annotation, it discloses that the call can cost money, requires adataforseo_spend, is bounded by job and monthly caps, and may block pending approval. It also names what is returned (job uuid, status, estimate, spent), which is substantial behavioral context for a mutating, budget-affecting tool.

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 cost warning is front-loaded in the first sentence, followed by the prerequisite, the constraints, and the return shape in a compact sequence. Every sentence carries information, with only slight density cost from packing auth, caps, and approval into one clause.

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?

For a two-parameter job-creation tool with no output schema, the description covers cost, credential requirement, caps, approval gating, and return values. An agent has everything needed to decide whether and how to invoke it.

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 description coverage is 100%, and the schema already documents the kind enum and the options object including the 'budgets and permissions cannot be overridden' constraint. The description's only added signal is reusing the same kind/options as the estimate call, so baseline 3 applies.

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?

The description gives a concrete verb and resource ('starts background work') and immediately frames it as a cost-incurring job creation step, with the kind enum in the schema supplying the job types. It clearly contrasts with adataforseo.estimate as the dry-run alternative, though 'background work' itself is generic until the schema is read.

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 states an explicit prerequisite workflow: call adataforseo.estimate with the same kind and options first. It also explains that unknown or high estimates are gated for approval, which tells the agent what to expect after calling. It does not spell out a when-not-to-use condition, but the estimate-first routing covers the main decision.

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