Skip to main content
Glama
Sign In

Howseen

by ai.howseen
OverviewDiscussionsAdmin

Get action plan

get_action_plan
Read-only

Prioritized actions to raise the brand's AI visibility (off-page: get listed on the pages AI cites; content: answer uncovered buyer questions; technical: site fixes, incl. links:<article_id> = link a new article from 3 related pages, with copy-ready sentences in links.pages; setup: connections), ranked 20/80 like the dashboard Action plan with the same inputs, with steps and state. For just the single next step, use get_next_action.

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

Input Schema

NameRequiredDescriptionDefault
toNoEnd date YYYY-MM-DD. Default: now.
fromNoStart date YYYY-MM-DD. Default: all time.
langNoLanguage of the action texts (default en).
brandNoBrand id, name or domain (from list_brands). Optional when the account has a single brand.
limitNoMax items to return (default 10, max 50).
engineNoOptional AI engine filter, comma separated: chatgpt, gemini, perplexity, ai_overviews, ai_mode. Default: all engines.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare this is a read-only, non-destructive, closed-world call, so the safety profile is covered. The description adds real value by explaining the 20/80 ranking mirrors the dashboard and that results include steps and state, plus what the technical link action returns (copy-ready sentences in links.pages). It still says nothing about pagination or result ordering beyond the ranking.

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?

Everything is packed into one sentence that is front-loaded with the purpose and the alternative routing at the end. It is dense but each clause (categories, ranking, links:<article_id> semantics) carries distinct information; the nested parentheses make it slightly hard to parse but nothing is wasted.

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, the description does explain the shape of results (ranked items with steps and state, and the links.pages payload), which is the key gap it needs to fill. It stops short of describing the full item structure or how state values are represented, leaving the agent with a partial picture of a fairly complex planning 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 to/from/lang/brand/limit/engine are already fully documented with defaults and the engine enum. The description adds no meaning beyond the schema for any parameter, so the baseline 3 applies.

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 names a specific resource (prioritized actions) and states the goal (raise the brand's AI visibility), then enumerates the action categories — off-page, content, technical, setup — and the 20/80 ranking model. It explicitly distinguishes itself from get_next_action, so an agent can choose without opening either schema.

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 a clear selection rule: use this for the full ranked plan, use get_next_action for just the single next step. It doesn't cover exclusions against near-neighbors like get_content_plan or get_easiest_wins, but the primary alternative is handled explicitly.

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

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