Skip to main content
Glama

get_content_publishing_limit

Check remaining daily Instagram posts to avoid publishing limits. Determine how many more posts you can publish within the 24-hour period.

Instructions

Check how many posts you can still publish today. Instagram limits content publishing per 24-hour period.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the get_content_publishing_limit method in the InstagramClient class, which makes a GET request to the Graph API.
    async getContentPublishingLimit(
      accountId?: string
    ): Promise<IGPublishingLimit> {
      const id = accountId ?? this.aid();
      const data = await this.request(
        "GET",
        `${id}/content_publishing_limit`,
        { params: { fields: "quota_usage,config,quota_duration" } }
      );
      return data.data?.[0] ?? {};
    }
  • The tool handler case that calls c.getContentPublishingLimit() when the 'get_content_publishing_limit' tool is invoked.
    case "get_content_publishing_limit":
      return JSON.stringify(await c.getContentPublishingLimit(), null, 2);
  • src/index.ts:142-146 (registration)
    The registration of the 'get_content_publishing_limit' tool in the TOOLS array, including its description and input schema.
      name: "get_content_publishing_limit",
      description:
        "Check how many posts you can still publish today. Instagram limits content publishing per 24-hour period.",
      inputSchema: { type: "object" as const, properties: {} },
    },
Behavior2/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 of behavioral disclosure. It mentions Instagram's 24-hour limit, which is useful context, but it does not describe the return format (e.g., numeric count, percentage), error conditions, or authentication requirements, leaving significant gaps for a tool that likely involves rate-limiting checks.

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 two sentences with zero waste: the first sentence states the purpose, and the second provides essential context about Instagram's limits. It is front-loaded and appropriately sized for a simple tool.

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

Completeness3/5

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

Given the tool's complexity (simple query with 0 parameters) and lack of annotations and output schema, the description is minimally complete. It explains what the tool does and the platform constraint, but without annotations or output schema, it should ideally describe the return value or behavior more explicitly to fully guide 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 0 parameters, and schema description coverage is 100%, so there is no need for parameter details in the description. The description appropriately avoids discussing parameters, earning a baseline score of 4 for not adding unnecessary information.

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's purpose with a specific verb ('Check') and resource ('how many posts you can still publish today'), and it distinguishes itself from siblings by focusing on publishing limits rather than content retrieval, posting, or account management operations.

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?

The description provides clear context for when to use this tool ('today' and 'per 24-hour period'), but it does not explicitly state when not to use it or name alternatives among the sibling tools (e.g., it doesn't contrast with publishing tools like publish_media).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mcpware/instagram-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server