Skip to main content
Glama

PostNitro

by ai.postnitro.mcp

Save Default Settings

postnitro_set_defaults
DestructiveIdempotent

Save default templateId, brandId, presetId, and responseType so you don't have to provide them every time.

These defaults persist across sessions. Any generate/import tool will automatically use them when those parameters are not explicitly provided.

Typical first-time setup workflow:

  1. Call postnitro_list_templates → pick a template

  2. Call postnitro_list_brands → pick a brand

  3. Call postnitro_list_ai_presets → pick a preset

  4. Call postnitro_set_defaults with the chosen IDs

  5. From now on, just call generate/import without specifying IDs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandIdNoDefault brand ID (get from postnitro_list_brands)
presetIdNoDefault AI preset ID (get from postnitro_list_ai_presets)
templateIdNoDefault template ID (get from postnitro_list_templates)
responseTypeNoDefault output format. 'DESIGN' creates the design with no rendered file (fastest); 'PDF'/'PNG' return a rendered file. 'MP4' cannot be saved as a default because it only applies to video posts — pass it per call on the video tools instead (a saved 'PDF'/'PNG' default is treated as 'DESIGN' there).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesConfirmation message
successYes
defaultsYesEvery default now stored, merged with previously saved values

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description adds useful behavioral context by stating that defaults persist and that MP4 cannot be saved as a default, which clarifies limits on future tool calls. The destructive and idempotent hints are already declared in annotations, and the description does not contradict them.

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 concise and well-structured, with a short explanatory paragraph followed by a clear numbered workflow. No redundant or fluff content is present.

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?

Given the high schema coverage and explicit annotations, the description provides enough context for correct use. It explains persistence, how defaults are consumed, and important exceptions, though it does not describe the exact return value; this is acceptable since an output schema is present.

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?

Input schema coverage is 100% with detailed descriptions for each parameter, including special notes on responseType behavior. The tool description reinforces that all parameters are optional and sourced from list tools, adding practical guidance beyond 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?

Clearly states that the tool saves default templateId, brandId, presetId, and responseType, and explains that these defaults are then used automatically by generate/import tools. This distinguishes it from sibling tools like postnitro_get_defaults and the individual generation tools.

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?

Provides a practical first-time setup workflow and explains that defaults persist across sessions, so users know when to call this tool before running generate/import operations. It could be slightly stronger by explicitly contrasting with postnitro_get_defaults, but the usage context is clear.

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

All PostNitro toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

Most tools are clearly separated by verb and noun (generate_carousel vs generate_image vs generate_video, import_* vs generate_*). The generic convenience names like generate_and_wait and import_and_wait are slightly ambiguous, but their descriptions and the _wait/_schedule suffixes make them distinguishable.

Naming Consistency4/5

All tools share the postnitro_ prefix and snake_case verb-first convention. A few compound names (generate_and_schedule, import_and_wait) break the strict verb_noun pattern, but the convention is otherwise consistent and predictable.

Tool Count2/5

With 35 tools, the surface exceeds the rubric's 25+ 'too many' threshold. Many entries are convenience wrappers (_wait, _and_schedule) around the same core operations and could be consolidated to reduce overload.

Completeness4/5

The domain is well covered: generation, import, output retrieval, scheduling, brands, social accounts, audio, templates, presets, and defaults. Minor gaps remain (no delete_brand, no upload/connect for audio/social accounts), but those are largely external or non-critical.

Resources