AutoPoster AI

Get Platform Rules and Limits

autoposter_get_rules

Read-only

Returns platform publishing constraints including character limits, media format requirements, and guidelines.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`guidelines`	Yes	Publishing guidelines and tips.
`postFormats`	No	Supported post format variants per platform (post, reel, story, shorts).
`captionLimits`	Yes	Character limits per platform.
`mediaRequirements`	Yes	Platform media requirements and constraints.
`automatedSafeguards`	No	Automated media and caption processing safeguards.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 10, 2026

addedOutput schema / properties / postFormats

Added value: +{
+  "description": "Supported post format variants per platform (post, reel, story, shorts).",
+  "type": "object"
+}

Changed1 schema field changedOct 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "automatedSafeguards": {
+      "description": "Automated media and caption processing safeguards.",
+      "type": "object"
+    },
+    "captionLimits": {
+      "description": "Character limits per platform.",
+      "type": "object"
+    },
+    "guidelines": {
+      "description": "Publishing guidelines and tips.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "mediaRequirements": {
+      "description": "Platform media requirements and constraints.",
+      "type": "object"
+    }
+  },
+  "required": [
+    "captionLimits",
+    "mediaRequirements",
+    "guidelines"
+  ],
+  "type": "object"
+}

First observedOct 7, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds that the payload is constraint metadata, but says nothing about freshness (whether platform rules are live or cached) or scope across platforms. With annotations carrying the safety profile, this is adequate but thin.

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?

One compact sentence with the resource front-loaded and no filler. 'Guidelines' is mildly vague but the earlier enumeration carries the meaning.

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?

An output schema exists, so return structure need not be spelled out, and there are no parameters to document. For a simple read-only getter this is nearly complete; only the absence of when-to-call guidance leaves a small gap.

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?

The tool takes zero parameters, so there is no parameter semantics to explain; baseline 4 applies. The description correctly implies a parameterless, fetch-everything call rather than suggesting a platform filter that does not exist.

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

Purpose4/5

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

States a clear verb ('Returns') and a well-scoped resource ('platform publishing constraints') and enumerates the content types (character limits, media format requirements, guidelines). It is clearly distinct from the write/upload/media siblings, though it does not name any sibling explicitly.

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?

Usage is only implied: an agent can infer this should be consulted before posting or uploading to check limits, but the description never states when to call it or what it replaces. No prerequisites or exclusions are given.

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

All AutoPoster AI 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?