Skip to main content
Glama
Sign In
PostKing MCP Server

PostKing MCP Server

by bitsandtea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

pick_post_visual

Selects a visual for a post on a given platform by passing template style, asset ID, or variant, and returns an edit link to refine it.

Instructions

Select a visual for a post on a given platform. Use the chosen option's pickArgs from generate_post_visual_options VERBATIM — for card/quote templates that means passing kind + style + variant together; for a library/smart asset or a stock photo, pass the assetId or slot from its pickArgs. Do not invent style names. variant is a 1-based template variant index. Includes editInVisualEditor: a direct URL to edit the post in the visual editor (when active brand is set).

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": {
      "postId": "<postId>",
      "platform": "<platform>"
    },
    "name": "pick_post_visual"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoVisual kind, taken verbatim from the chosen option's pickArgs. REQUIRED when picking a card or quote template style (e.g. kind:'quote' with style:'gradient-bold'). If omitted, the server assumes 'card' and will reject quote styles.
slotNoInternal template slot key (advanced)
styleNoTemplate style name from generate_post_visual_options
postIdYesPost ID
assetIdNoLibrary asset ID from list_assets
variantNoTemplate variant index
platformYesTarget platform, e.g. 'linkedin'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.7

TDQS

A4.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It explains pickArgs requirements and mentions the editInVisualEditor result field, but it does not disclose whether this is a mutating action that overwrites an existing visual, what permissions or brand context are required beyond 'active brand is set', or error behavior. This is a partial but not complete behavioral picture.

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?

Three sentences, all information-dense and front-loaded: the first states the core purpose, the second details exact usage mechanics, and the third notes a useful return field. Every sentence earns its place with zero filler.

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?

The description covers the essential input semantics and one return field, but since there is no output schema and no annotations, it could go further by stating the full response shape or whether the call replaces/updates the existing post visual. It is close to complete for correct invocation, though not fully comprehensive.

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

Parameters5/5

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

Even though schema coverage is 100%, the description adds significant meaning beyond the bare schema descriptions: variant is a 1-based index, kind is required for card/quote templates, and parameters must come directly from generate_post_visual_options pickArgs. This is exactly the kind of semantic clarification agents need.

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 a specific verb+resource: 'Select a visual for a post on a given platform.' It clearly differentiates from sibling tools like regenerate_post_visual and clear_post_visual by referencing pickArgs from generate_post_visual_options and mentioning the editInVisualEditor URL field.

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

Usage Guidelines5/5

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

The description provides explicit usage rules: use pickArgs VERBATIM, pass kind+style+variant together for card/quote templates, pass assetId or slot for library/smart/stock assets, and do not invent style names. This gives clear when/how guidance and implicitly distinguishes from alternative visual tools.

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