Skip to main content
Glama
adbutler

AdButler MCP Server

Official
by adbutler

create_manager

Create a new manager account in AdButler with specified name, email, passwords, and granular permissions for managing users, links, media, billing, and more.

Instructions

Create a new manager

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesManager name
emailYesManager email address
notesNoNotes about the manager
passwordNoLogin password (min 8 chars with upper, lower, number). Random if blank.
positionNoManager position in organization
is_enabledNoWhether the manager account is enabled
can_manage_linksNoCan create/edit/delete active tracking links
can_manage_mediaNoCan manage creatives and media groups
can_manage_usersNoCan manage user accounts and permissions
publisher_accessNoPublisher access level
statistics_accessNoStatistics access level
can_manage_biddersNoCan manage bidders
can_manage_billingNoCan view invoices and billing
can_manage_targetsNoCan assign/remove targets from placements
can_manage_ticketsNoCan create/view support tickets
can_manage_contractsNoCan manage contracts and templates
can_manage_data_keysNoCan manage data keys
can_manage_product_dbNoCan manage product catalogs
can_manage_self_serveNoCan manage Self-Serve portals
publisher_access_listNoPublisher IDs accessible when publisher_access is "specific"
can_manage_programmaticNoCan manage demand sources and PMP deals
can_manage_admin_api_accessNoCan manage API keys
can_assign_campaigns_directlyNoCan assign campaigns directly to zones
can_manage_native_ad_templatesNoCan manage native templates
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only repeats the tool name. It does not mention side effects, required permissions, or consequences of creating a manager (e.g., sending an email, creating a login).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise with no wasted words, but it is under-specified. It essentially restates the tool name without adding contextual structure, which limits its usefulness.

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

Completeness2/5

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

Given the tool has 24 parameters and no output schema, the description is far too minimal to provide adequate context. It fails to clarify what a manager is in this system, when to use it, or what the result of creation implies.

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?

The input schema has 100% description coverage for all 24 parameters, so the baseline is 3. The tool description adds no parameter-specific meaning, but the schema adequately documents each field's purpose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'Create' and a resource 'manager', clearly indicating the tool creates a manager. However, it does not differentiate from other create tools like create_user or create_bidder, so it lacks sibling differentiation.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or scenarios where a different tool would be more appropriate.

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/adbutler/mcp-server'

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