Kampalo

SEO action plan

search_get_action_plan

Read-only

Ranked SEO action plan: keyword clusters with one action each (create a page, improve a page, push to top 3, fix title, target the AI answer), priority, search volume, your exact position and the evidence. Use for "what should I do next for SEO" or "what pages should I build".

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

Input Schema

Name	Required	Description	Default
`url`	No
`days`	No
`limit`	No
`action`	No
`status`	No
`date_to`	No
`page_id`	No
`sort_by`	No
`user_id`	No
`site_url`	No
`client_id`	No
`date_from`	No
`ad_account`	No
`ig_user_id`	No
`user_email`	No
`range_preset`	No
`activity_only`	No
`campaign_name`	No
`property_name`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 27, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful output composition details—clusters, actions, priority, volume, position, evidence—but does not disclose auth needs, rate limits, pagination, or other invocation behavior.

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?

The description is two efficient sentences: the first front-loads what the tool returns, and the second front-loads when to use it. There is no redundant restatement of the title or annotation data.

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

Completeness2/5

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

The description is complete about the output concept and use cases, which is helpful. However, for a tool with 19 undocumented parameters and no schema descriptions, it leaves the agent without guidance on how to scope, filter, sort, or target the action plan.

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

Parameters1/5

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

The tool has 19 optional parameters with 0% schema description coverage, and the description does not explain any of them. Parameters such as action, status, sort_by, days, range_preset, site_url, and page_id remain semantically opaque, which is a significant gap for invocation.

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 resource and output: a ranked SEO action plan with keyword clusters, one action per cluster, priority, search volume, position, and evidence. It distinguishes this from sibling search tools by emphasizing recommended actions rather than raw metrics or queries.

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 use cases: "what should I do next for SEO" and "what pages should I build." It does not explicitly name alternatives or say when not to use it, so it stops short of the top score.

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

All Kampalo tools Inspect

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.