Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Matrix Tool

adataforseo.matrix

Map one target page per country, place, deal, type, and language to compare real and raw demand, SERP difficulty, priority score, tier, and the serving or proposed URL.

Instructions

Read-only. The page matrix: one target page per country, place, deal, type and language with real (deduplicated) demand, raw demand, SERP difficulty, priority score and tier, and the document serving it or the proposed URL.

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": "adataforseo.matrix"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage code
tierNoP1, P2 or P3
statusNoexists, not_indexed, missing or needs_locale
countryNoTwo-letter market, e.g. CZ

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.4

TDQS

B3.2/5.0
Behavior3/5

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

Since no annotations are provided, the description carries the full behavioral burden. It does disclose that the tool is 'Read-only' and lists the returned fields, which is useful, but it does not cover permissions, refresh behavior, pagination, sorting, or filtering defaults.

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 description is compact and front-loads the read-only nature before listing the matrix contents. The single long sentence is dense but efficient, with little wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description does a fair job of listing the output fields and the grain of the matrix. However, it omits important context such as how filters affect results, default behavior, ordering, and limits, leaving meaningful gaps for a 4-filter report tool.

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%, so the schema already documents lang, tier, status, and country. The description mentions country and language as matrix dimensions but adds no filter-specific meaning, defaults, or usage semantics beyond the schema baseline.

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 clearly identifies the resource as a page matrix and enumerates the dimensions and metrics it contains, so an agent can understand what data it returns. It lacks an explicit verb and does not distinguish itself from siblings such as coverage or rankings, which keeps it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool, when not to use it, or which sibling tool to choose instead. The description only states what the matrix contains, leaving the agent to infer usage context.

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