Skip to main content
Glama

Pith - Instagram Publishing

by day.pith
OverviewDiscussionsAdmin

Connect an Instagram account

connect_instagram
Idempotent

Get a one-time link that connects the user's Instagram Business/Creator account to Pith so publish_post can post to it. No handle is needed — the account that gets connected is whichever one the user authorizes on Instagram, so call this as soon as whoami shows no accounts instead of asking the user for a username. Show the user the returned connectUrl exactly as given (do not rewrite or shorten it), tell them to open it and approve on Instagram, and when they say they're done call whoami to confirm. The link expires in 10 minutes and works once — call this tool again for a fresh one. Requires an Instagram professional account; personal accounts cannot use Instagram's publishing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
handleNoOptional. The user's Instagram handle (with or without @), only if they told you it. Never guess or use a placeholder — omit it instead; Pith uses whichever account the user authorizes.
contextYesExplain why you are calling this tool and how it fits into the business owner's goal for their Instagram presence. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include personal data, credentials, or the text of a draft. Example (20 words): "Reviewing the pending drafts before approving today's story, checking the caption matches the photo the owner expects."

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / handle / description
      Previous value: -"The Instagram handle to connect (with or without @). Must be the account you'll authorize on Instagram."New value: +"Optional. The user's Instagram handle (with or without @), only if they told you it. Never guess or use a placeholder — omit it instead; Pith uses whichever account the user authorizes."
    • changedInput schema / required
      Previous value: -[
-  "handle",
-  "context"
-]New value: +[
+  "context"
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare non-read-only, non-destructive, open-world, idempotent behavior. The description adds meaningful operational detail: the link is one-time, expires in 10 minutes, connects whichever account the user authorizes, and must be displayed verbatim. No contradiction with annotations.

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 front-loaded with the main purpose and then flows into trigger, user-facing steps, expiry, and account requirements. Every sentence contributes a distinct operational fact; no filler or repetition.

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?

Despite no output schema, it tells the agent what to expect (connectUrl), how to handle it, when to confirm via whoami, and the account prerequisite. For a two-parameter tool with a rich schema and strong annotations, nothing essential is missing.

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%, so the schema already documents both handle and context thoroughly. The description adds the 'no handle needed' clarification, which reinforces the schema, but does not materially augment parameter meaning beyond the structured definitions.

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 action ('Get a one-time link') and resource (connects the user's Instagram Business/Creator account to Pith), and explicitly frames it as the prerequisite for publish_post. This distinguishes it from siblings like whoami and publish_post by naming the dependency and trigger condition.

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

Usage Guidelines5/5

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

It gives an explicit call trigger ('as soon as whoami shows no accounts'), says not to ask for a username, and directs the follow-up step (call whoami to confirm). It also states constraints: Instagram professional account required, personal accounts cannot use the publishing API, and the link expires in 10 minutes.

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

All Pith - Instagram Publishing toolsInspect
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