get_blog_postA blog post's full text (plain text) by slug.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | ||
| locale | No | Storefront locale such as en-GB (default), en-US, de, fr-FR, es-ES, it-IT, nl-NL, pl. Controls product names, slugs and prices. |
| Name | Required | Description | Default |
|---|---|---|---|
| post | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / post / properties / content / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / post / properties / content / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / post / properties / excerpt / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / post / properties / excerpt / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "post": {
+ "additionalProperties": false,
+ "properties": {
+ "categories": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "content": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "The post body as plain text."
+ },
+ "excerpt": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "id": {
+ "type": "number"
+ },
+ "published_at": {
+ "type": "string"
+ },
+ "slug": {
+ "type": "string"
+ },
+ "title": {
+ "type": "string"
+ },
+ "url": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "title",
+ "slug",
+ "url",
+ "excerpt",
+ "published_at",
+ "categories",
+ "content"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "post"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds that the returned content is plain text rather than HTML/markdown, which is useful, but says nothing about what happens with an unknown slug or an invalid locale.
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?
A single fragment that front-loads the resource and the return format with zero waste. It is arguably too terse, but nothing is redundant.
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?
An output schema exists, so return structure needn't be described, and locale is documented in the schema. However, for a tool whose locale parameter 'controls product names, slugs and prices', the description never notes whether locale affects the post lookup, which is a meaningful gap for correct invocation.
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 coverage is 50%: locale is well documented in the schema, while slug has no description but is self-evident and constrained (1-200 chars). The description's 'by slug' confirms the lookup key but adds no meaning beyond the schema.
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?
States a specific resource (blog post) and what it returns (full text, plain text) retrieved by slug. It is clearly distinguishable from search_blog_posts, though it does not name that sibling 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?
The 'by slug' phrase implies this is a single-item exact-lookup versus a search, but there is no explicit when-to-use/when-not guidance or reference to search_blog_posts as the alternative for discovery.
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.