mixpost-mcp-server

mixpost_get_account

Retrieve detailed information for a specific social media account by providing its UUID.

Instructions

Get details of a specific social media account

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": {
      "accountUuid": "<accountUuid>"
    },
    "name": "mixpost_get_account"
  }
}

Input Schema

Name	Required	Description	Default
`accountUuid`	Yes	The UUID of the account to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 1, 2026

TDQS

A3.8/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 for conveying safety and side effects. 'Get details' strongly implies a read-only operation, but the description does not explicitly state that it is non-destructive, nor does it disclose error behavior (e.g., 404 if not found) or whether any cached data is involved. It provides a basic level of transparency.

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 a single, clear sentence with no redundant words. It front-loads the primary action ('Get details') and resource ('specific social media account'), making it highly efficient and easy to parse.

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 tool is simple with only one parameter and no output schema or annotations. The description adequately communicates the purpose, but it does not specify what 'details' includes or what the response structure looks like. Given the tool's simplicity, this is acceptable, though additional information on return format would make it fully complete.

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

Parameters3/5

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

Schema description coverage is 100% for the single parameter 'accountUuid', which already fully explains what to pass. The description adds no extra meaning beyond the schema, aligning with the baseline score of 3 for high coverage.

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 clearly states the tool retrieves details of a specific social media account, with the word 'specific' indicating a single entity by ID. This distinguishes it from sibling tools like mixpost_list_accounts, making the purpose unambiguous.

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

Usage Guidelines3/5

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

The description implies usage for retrieving a single account's details but provides no explicit guidance on when to use this tool versus alternatives (e.g., list_accounts) or any prerequisites/exclusions. The usage context is inferred from the verb and resource, not stated directly.

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