Retrieve a specific goal by providing its UUID and the website ID. Returns detailed goal resource information.
Get a specific goal by ID.
Args:
goal_id: Goal UUID
website_id: Website/App UUID
Returns:
Goal resource
| Name | Required | Description | Default |
|---|---|---|---|
| goal_id | Yes | ||
| website_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations include readOnlyHint=true, indicating a safe read operation. The description adds minimal behavioral context beyond that, stating it returns a 'Goal resource'. This is adequate but not exceptional.
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 concise with three lines: purpose, arguments, and returns. No extraneous words, effectively front-loaded.
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?
Given the existence of an output schema (indicated by context signals) and the straightforward nature of a get-by-ID operation, the description sufficiently covers the tool's functionality. Minor edge cases (e.g., missing IDs) are not addressed but are standard for such tools.
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?
With 0% schema description coverage, the description compensates by labeling parameters as 'Goal UUID' and 'Website/App UUID', adding meaningful context beyond type 'string'.
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 explicitly states 'Get a specific goal by ID', using a clear verb and resource. It naturally distinguishes itself from the sibling 'analytics_goals_list' which retrieves multiple goals.
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?
No guidance is provided on when to use this tool versus alternatives, when not to use it, or any prerequisites. The agent must infer usage solely from the verb 'Get'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/PiwikPRO/mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server