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 / (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 establish this as a safe read-only operation (readOnlyHint=true, destructiveHint=false). The description adds useful context that the response is full plain text and that lookup is by slug, but it does not cover not-found behavior, locale effects, or any limits.
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 one short sentence with no filler, yet it includes the resource, identifier, and return format. It is terse without being under-specified.
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 fetch with an output schema and annotation-covered safety profile, the description plus schema is sufficient. The main omission is not pointing to search_blog_posts for discovery, but that is more of a usage-guideline gap than a completeness gap.
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 schema provides a detailed description for locale but leaves slug undocumented; the description's 'by slug' gives slug its semantic role as the identifier. Locale is not mentioned in the description, but the schema covers it, so combined parameter understanding is adequate.
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 identifies the resource ('a blog post's full text') and the lookup key ('by slug'), and specifies the output format ('plain text'). It is distinct from search_blog_posts by implying direct slug-based retrieval, though it never explicitly names that sibling.
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 phrase 'by slug' implies this tool is for retrieving a known post rather than discovering one, giving a basic usage signal. However, there is no explicit guidance about when to prefer this over search_blog_posts, and no exclusions or prerequisites are stated.
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.