Blog2Social - Social Media Publishing

Retrieve own published post performance insights

posts.insights

Use this tool when the user asks for performance metrics or analytics for your own published social media post.

It retrieves the latest available performance insights and associated credit information for the specified published post.

It requires the public publish_url returned after a successful posts.publish_post operation. It works only for supported social networks and account types with tracking enabled.

Available metrics depend on the social network, account type, published post, tracking availability, and data returned by the endpoint. Not all metrics are available for every post or network.

Report only metrics actually returned by the server. Do not interpret missing metrics as zero or invent unavailable performance data.

The request may deduct credits according to the account and network pricing. Consider the credit cost before making the request.

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": {
      "post_url": "<post_url>"
    },
    "name": "posts.insights"
  }
}

Input Schema

Name	Required	Description	Default
`post_url`	Yes	Public URL of the published post whose insights should be retrieved.

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 27, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description adds substantial context beyond the annotations: it discloses that metrics availability varies by network, account type, post, and tracking; warns not to interpret missing metrics as zero; and notes that the request may deduct credits according to pricing. These are important behavioral details for a non-read-only, open-world tool with credit side effects. The readOnlyHint=false annotation is consistent with the description's explicit mention of credit deduction.

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

Conciseness4/5

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

The description is front-loaded with the usage trigger and is organized around purpose, prerequisites, limitations, and credit cost. It is somewhat longer than necessary, but the caveats about missing metrics and credit deduction justify most of the length.

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

Completeness5/5

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

Given the presence of an output schema and annotations, the description is complete enough for correct invocation. It covers when to use the tool, the required URL provenance, supported-network limitations, missing-metric handling, and credit implications without needing to explain return values.

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%, so the single post_url parameter is already documented as the public URL of the published post. The description adds useful meaning by specifying that it must be the publish_url returned after a successful posts.publish_post operation, not just any post URL.

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 states a specific verb and resource: retrieve performance metrics/analytics for your own published social media post. It clearly scopes the tool to published posts using the public publish_url returned by posts.publish_post, which distinguishes it from sibling tools like account.overview or posts.publish_post.

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?

It gives an explicit trigger: use when the user asks for performance metrics or analytics for your own published post. It also states prerequisites and limitations, including needing the publish_url from posts.publish_post and working only for supported networks/account types with tracking enabled. It does not explicitly name alternative tools for account-level versus post-level analytics, but the usage context is clear.

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

All Blog2Social - Social Media Publishing tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?