shoptet_get_bannerRetrieves the HTML content and settings of a single Shoptet e-shop banner by its ID, so you can inspect or verify banner details before making changes.
HTML content and settings of one banner.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare this as a read-only, idempotent, non-destructive operation, so the safety profile is covered. The description adds useful context that the response includes HTML content and settings, but it does not mention permissions, rate limits, or any other behavioral traits beyond what annotations provide.
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 short sentence with no wasted words, and the resource scope is front-loaded. However, the fragmentary phrasing leaves out information that would make the sentence more actionable.
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 simple read-only tool with one parameter, the description is adequate in stating that one banner is retrieved along with its HTML and settings. It is still missing how to obtain the banner ID and any additional return context, which matters because there is no output schema.
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?
Schema description coverage is 0%, and there is only one required id parameter. The description implies that the ID selects a single banner, but it does not explain the ID format, where the ID comes from, or how to obtain it, so it only minimally compensates for the undocumented parameter.
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 identifies the resource and scope as one banner, and states that it returns HTML content and settings. The singular 'one banner' implicitly distinguishes it from the sibling list_banners tool, though it does not name the alternative explicitly.
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?
There is no explicit guidance on when to use this tool versus shoptet_list_banners, shoptet_get_html_codes, or other retrieval siblings. The singular scope implies retrieval by ID, but no conditions, prerequisites, or exclusions are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.