get_personasThe 2-4 buyer personas inferred from this business's measured questions, the way AI models would describe each buyer type, with the exact tracked questions each persona asks. Read-only.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description goes beyond the readOnlyHint annotation by explaining that the personas are inferred, that the count ranges from 2-4, that the style is how AI models would describe buyer types, and that exact tracked questions are included. This added context clarifies what kind of data to expect and how it was derived, with no contradiction to the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that front-loads the core output ('2-4 buyer personas') and packs in source, style, and included data without filler. The appended 'Read-only' is redundant with annotations but does not harm conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless, read-only tool with no output schema, the description tells the agent everything needed to know before calling: the range of personas, their origin, the descriptive style, and that each persona carries its tracked questions. No critical behavioral or shape information is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the empty schema fully covers parameter expectations. Per the baseline for 0-parameter tools, the description does not need to explain parameters; it adds no parameter details but none are required.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states that the tool returns 2-4 buyer personas inferred from measured questions, describes how they are framed (as AI models would describe each buyer type), and notes each persona includes the exact tracked questions they ask. This is a specific, unambiguous definition of the resource and its content, and it is distinct among the sibling get_* tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance about when to use this tool versus the many sibling tools. It does not state a use case, prerequisites, or alternatives, so an agent must infer appropriateness solely from the name and content description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clearly distinct objects: answers, trajectories, citations, mentions, traffic, scores, and briefs. A few pairs like get_citation_sources vs get_source_profile and get_rivals vs get_share_of_voice overlap thematically, but their descriptions clarify different granularity and purpose.
All 16 tools follow an identical get_ + snake_case noun phrase pattern, such as get_agent_view, get_share_of_voice, and get_question_trajectories. This makes the tool set highly predictable and easy to navigate.
At 16 tools, the set sits just above the ideal 3-15 range, but each tool addresses a distinct facet of AI visibility monitoring. The count feels justified rather than bloated, though it is slightly heavy for a read-only monitor.
The suite covers the full read-only monitoring lifecycle: visibility scores, raw answers, question histories, competitor comparisons, cited sources, mentions, traffic, benchmarks, action plans, personas, and content briefs. There are no obvious dead ends or missing core operations for the stated purpose.