get_blogUse this when someone asks about one blog's setup, such as its domain, default language or languages. Returns the blog's id, name, custom domain, default locale, locales, cover image URL and dates, by id or name. Not for a visual overview with recent posts.
| Name | Required | Description | Default |
|---|---|---|---|
| idOrName | Yes | Blog id, or the blog's name |
| Name | Required | Description | Default |
|---|---|---|---|
| blog | Yes | ||
| status | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / blog / anyOfPrevious value: -[
- {
- "additionalProperties": false,
- "properties": {
- "coverUrl": {
- "anyOf": [
- {
- "maxLength": 2048,
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "created": {
- "anyOf": [
- {
- "maxLength": 100,
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "customDomain": {
- "anyOf": [
- {
- "maxLength": 300,
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "defaultLocale": {
- "anyOf": [
- {
- "maxLength": 50,
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "edited": {
- "$ref": "#/properties/blog/anyOf/0/properties/created"
- },
- "id": {
- "anyOf": [
- {
- "maxLength": 200,
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "locales": {
- "items": {
- "maxLength": 50,
- "type": "string"
- },
- "maxItems": 100,
- "type": "array"
- },
- "localesTruncated": {
- "type": "boolean"
- },
- "name": {
- "anyOf": [
- {
- "maxLength": 200,
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- }
- },
- "required": [
- "id",
- "name",
- "customDomain",
- "defaultLocale",
- "locales",
- "localesTruncated",
- "coverUrl",
- "created",
- "edited"
- ],
- "type": "object"
- },
- {
- "type": "null"
- }
-]New value: +[
+ {
+ "additionalProperties": false,
+ "properties": {
+ "coverUrl": {
+ "$ref": "#/properties/blog/anyOf/0/properties/logoUrl"
+ },
+ "created": {
+ "anyOf": [
+ {
+ "maxLength": 100,
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "customDomain": {
+ "anyOf": [
+ {
+ "maxLength": 300,
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "defaultLocale": {
+ "anyOf": [
+ {
+ "maxLength": 50,
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "edited": {
+ "$ref": "#/properties/blog/anyOf/0/properties/created"
+ },
+ "id": {
+ "anyOf": [
+ {
+ "maxLength": 200,
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "locales": {
+ "items": {
+ "maxLength": 50,
+ "type": "string"
+ },
+ "maxItems": 100,
+ "type": "array"
+ },
+ "localesTruncated": {
+ "type": "boolean"
+ },
+ "logoUrl": {
+ "anyOf": [
+ {
+ "maxLength": 2048,
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "name": {
+ "anyOf": [
+ {
+ "maxLength": 200,
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ }
+ },
+ "required": [
+ "id",
+ "name",
+ "customDomain",
+ "logoUrl",
+ "defaultLocale",
+ "locales",
+ "localesTruncated",
+ "coverUrl",
+ "created",
+ "edited"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / idOrName / descriptionPrevious value: -"Blog id (uuid) or name"New value: +"Blog id, or the blog's name"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's main behavioral contribution is a list of returned fields, which overlaps with the existing output schema rather than adding new context such as lookup-failure behavior or case sensitivity of name matching.
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?
Three tight sentences, front-loaded with the usage condition followed by return contents and the exclusion. Every sentence carries routing or scoping information with no filler.
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 single-parameter read tool with full annotation coverage and an output schema, the description is nearly complete: purpose, trigger, and alternative are all present. The enumerated return fields are somewhat redundant with the output schema, but nothing an agent needs to call the tool correctly 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?
Schema coverage is 100% and the single idOrName parameter is already documented in the schema, so the baseline is 3. The phrase "by id or name" merely restates what the schema parameter says and adds no new syntax, format, or matching-semantics detail.
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 verb (get) and resource (blog details), lists the concrete fields returned (domain, default locale, locales, cover image, dates), and explicitly distinguishes itself from the visual sibling show_blog_overview. An agent can identify the tool without opening the schema.
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?
Gives an explicit trigger ("when someone asks about one blog's setup") and an explicit exclusion ("Not for a visual overview with recent posts"), which routes the agent to show_blog_overview for that case. Nothing is left to inference.
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.