Skip to main content
Glama
Sign In
Enterprise Threads MCP Server

Enterprise Threads MCP Server

by baguskto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_publishing_limit

Check your current publishing quotas and limits to determine how many more posts you can make on Threads.

Instructions

Check your current publishing quotas and limits

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_publishing_limit"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv5.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Check' strongly implies a read-only operation, but the description does not explicitly state that it has no side effects, does not consume quota, or that it returns data without altering state. It provides minimal but non-misleading behavioral information.

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, concise, and front-loaded sentence that clearly states the tool's purpose. Every word earns its place, and there is no redundancy or extraneous detail.

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 tool with no parameters and no output schema, the description provides adequate context for invocation. It clearly identifies what the tool does, though it could be slightly more detailed about the nature of the returned quotas (e.g., daily post limits vs. rate limits), which would improve completeness for an agent.

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 has zero parameters, and the schema coverage is 100% (vacuously). No parameter semantics are needed, and the description adds no parameter information, which is acceptable since there is nothing to clarify.

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 uses a specific verb ('Check') with a clear resource ('your current publishing quotas and limits'). It is easily distinguishable from sibling tools that perform actions (publish_thread, schedule_post) or retrieve other profile data (get_my_profile).

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 this tool is used to check publishing limits before posting, but it does not explicitly state when to use it or mention alternatives. There are no exclusions or context signals provided, so the usage context is only weakly implied.

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