Skip to main content
Glama

Nuntior

by com.nuntior.mcp
OverviewDiscussionsAdmin

Manage Multi-Tenant Brand Profiles

profiles_manage
Idempotent

Create, list, update, or delete isolated multi-tenant brand or client profiles within a Nuntior workspace, including default timezone, X Smart Link optimization strategy, and automatic media aspect-ratio fitting rules. Use this tool to segment social accounts by brand, business unit, or agency client so credentials and posts never mix across profiles. Returns the list of profiles or the newly created/updated/deleted Profile record persisted in Nuntior Cloud.

Input Schema

NameRequiredDescriptionDefault
nameNoHuman-readable brand, executive, or client display name for the profile (e.g. 'Allometrik Official' or 'Acme Corp').
actionYesProfile lifecycle operation to perform: 'list' all profiles in the workspace, 'create' a new isolated brand profile, 'update' an existing profile's settings, or 'delete' a profile by ID.
timezoneNoIANA timezone identifier (e.g. 'Europe/Madrid', 'America/New_York', 'Asia/Dubai') used for queue scheduling and best-time-to-post analytics.Europe/Madrid
profileIdNoTarget profile identifier (e.g. 'prof_allometrik'). Required for 'update' and 'delete' actions; optional custom ID when creating a profile.
handleSlugNoURL-friendly canonical handle slug (e.g. 'allometrik') used to verify social handle consistency across connected platforms.
autoAdjustMediaNoWhen true, automatically reframes and transcodes uploaded images and videos to match each destination social network's required aspect ratio (9:16, 16:9, 1:1, 4:5).
defaultXLinkStrategyNoDefault X (Twitter) link placement policy for this profile: 'first_reply' moves external URLs to an automatic 1st reply (saving 85% in X API link fees and avoiding reach penalties), 'inline' keeps links in the main post, and 'bio' references the profile bio link.first_reply

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / action / description
      Added value: +"Profile lifecycle operation to perform: 'list' all profiles in the workspace, 'create' a new isolated brand profile, 'update' an existing profile's settings, or 'delete' a profile by ID."
    • addedInput schema / properties / autoAdjustMedia / description
      Added value: +"When true, automatically reframes and transcodes uploaded images and videos to match each destination social network's required aspect ratio (9:16, 16:9, 1:1, 4:5)."
    • addedInput schema / properties / defaultXLinkStrategy / description
      Added value: +"Default X (Twitter) link placement policy for this profile: 'first_reply' moves external URLs to an automatic 1st reply (saving 85% in X API link fees and avoiding reach penalties), 'inline' keeps links in the main post, and 'bio' references the profile bio link."
    • changedInput schema / properties / handleSlug / description
      Previous value: -"URL-friendly slug"New value: +"URL-friendly canonical handle slug (e.g. 'allometrik') used to verify social handle consistency across connected platforms."
    • changedInput schema / properties / name / description
      Previous value: -"Brand or client display name"New value: +"Human-readable brand, executive, or client display name for the profile (e.g. 'Allometrik Official' or 'Acme Corp')."
    • changedInput schema / properties / profileId / description
      Previous value: -"Profile ID (for update/delete)"New value: +"Target profile identifier (e.g. 'prof_allometrik'). Required for 'update' and 'delete' actions; optional custom ID when creating a profile."
    • addedInput schema / properties / timezone / description
      Added value: +"IANA timezone identifier (e.g. 'Europe/Madrid', 'America/New_York', 'Asia/Dubai') used for queue scheduling and best-time-to-post analytics."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The description goes beyond safety hints by specifying the behavioral scope of the management, such as including 'default timezone' and 'automatic media aspect-ratio fitting rules.' It also explicitly clarifies the possible return values (list or a specific record).

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?

Although lengthy, the description is well-justified by the tool's complexity (7 parameters, multi-action support). The core function and major benefits are front-loaded into the first two sentences.

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?

Given the detailed input schema and annotations, the description is highly complete. It explains complex settings (like media fitting and link strategy) and confirms the expected output behavior, leaving no critical behavioral unknowns for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds substantial semantic value by explaining the *business impact* of specific parameters, such as the X Smart Link strategy 'saving 85% in X API link fees' and 'avoid[ing] reach penalties.' This context is far richer than the schema alone provides.

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 tool clearly states its purpose as managing isolated multi-tenant brand or client profiles using the specific verbs: create, list, update, or delete.

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 excellent context on *when* to use this tool—specifically for segmenting social accounts by brand, business unit, or agency client. While it doesn't name alternatives, the strong focus on isolation defines its necessary use case.

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

All Nuntior toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources