Pith - Instagram Publishing

Record what the owner wants from Pith

set_brief

DestructiveIdempotent

Record the owner's brief — what they want their daily posts to be about — on the Brand DNA. wants: up to 6 short directions in their words or the labels they picked from propose_brief; avoid: up to 6 things they never want to see; note: their own words (up to 400 characters). Arrays replace what was there. The brief WEIGHS what tomorrow's drafts are about across the week; it never makes every post about one thing. Pass keep=true to confirm the brief on file unchanged (the monthly review), or forget=true to remove it. Ask the owner; never invent a brief.

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": {
      "context": "<context>"
    },
    "name": "set_brief"
  }
}

Input Schema

Name	Required	Description
`keep`	No	true: the owner confirmed the brief on file still stands; nothing else is read.
`note`	No
`avoid`	No
`wants`	No
`forget`	No	true: remove the brief; nothing else is read.
`handle`	No	Instagram handle (with or without @). Omit for your default account.
`context`	Yes	Explain 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.

AddedNov 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description still adds real value by spelling out the failure mode: "Arrays replace what was there", and by clarifying that keep/forget read nothing else. It also explains the downstream effect (the brief weighs what drafts are about across the week, not every post). It stops short of covering precedence when keep and forget are both supplied, or what a partial update leaves untouched.

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 first sentence front-loads the purpose, and the per-field semantics follow in compact clauses. The semicolon-chained sentences are dense and the wants/avoid/note enumeration is glued together in one long line, but almost every clause carries information an agent needs.

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 7-parameter destructive mutation with no output schema, the description covers the meaningful operations (set, keep, forget), the replacement semantics, and the downstream effect on drafts. The uncovered gaps are the handle default and how the 400/6 figures relate to the schema's larger limits, both of which matter for correct invocation.

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 coverage is only 57%, and the description does add business meaning for wants, avoid, note, keep and forget. However its stated limits conflict with the schema: "up to 6" directions vs maxItems 12, note "up to 400 characters" vs maxLength 800, which could lead an agent to truncate unnecessarily or misread the real constraints. handle and context are left entirely to the schema.

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?

"Record the owner's brief ... on the Brand DNA" names a specific verb and resource, then enumerates what a brief consists of (wants/avoid/note). It implicitly separates itself from propose_brief by describing itself as recording the labels the owner picked there, so an agent can tell the two siblings apart.

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 explicit modes: populate wants/avoid/note to set a brief, keep=true for the monthly review of an unchanged brief, forget=true to remove it. It also states a hard precondition — "Ask the owner; never invent a brief" — which is exactly the routing/safety guidance an agent needs before calling.

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 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?