Skip to main content
Glama
Sign In
PostKing MCP Server

PostKing MCP Server

by bitsandtea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_blog_article

Retrieve a blog article by ID. Choose short, medium, or full detail for summary fields or complete content with preview and edit links.

Instructions

Fetch a blog article by ID. detail='short' returns id/title/slug/status; detail='medium' adds excerpt+wordCount+previewUrl+editUrl; detail='full' (default) returns the COMPLETE content plus previewUrl (GUI preview link) and editUrl (dashboard editor link). Pass maxContentChars only if you need to bound the body size; omit it to get the whole article.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "articleId": "<articleId>"
    },
    "name": "get_blog_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNoVerbosity of returned item(s): "short" = id + primary label + status (cheap list scan); "medium" = key summary fields + counts (a useful glance); "full" = the complete object. Default "full". Lists default to "short" — to zoom into one item, call its get/view tool with detail="medium" or "full".full
brandIdNoBrand ID (uses active brand if omitted)
articleIdYesBlog article ID
maxContentCharsNoOptional cap on the returned content body length (full detail only). Omit to return the ENTIRE article body. Use only to bound payload size for small clients.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.7

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden of disclosing behavior. It thoroughly explains the return contents for each detail level and the effect of maxContentChars. However, it does not explicitly state that the operation is read-only or describe error behavior, though 'fetch' implies safety.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences long, starts with the core action, and efficiently conveys the detail levels and maxContentChars guidance. Every sentence earns its place with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple fetch tool with no output schema and no annotations, the description covers the key behaviors: detail verbosity, field lists, and payload bounding. It does not mention brandId or error cases, but given the 100% schema coverage, this is acceptable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant meaning beyond the schema by enumerating the exact fields returned for each detail level and clarifying the purpose of maxContentChars. It does not discuss brandId, but the schema already covers it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Fetch a blog article by ID,' which is a specific verb and resource. It clearly distinguishes from sibling tools like update_blog_article, delete_blog_article, and list_blogs by focusing on single-article retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for fetching one article and provides explicit guidance on when to use maxContentChars ('only if you need to bound the body size'). It does not explicitly name alternatives like list_blogs for listing multiple articles, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools