Skip to main content
Glama
adbutler

AdButler MCP Server

Official
by adbutler

create_role

Create a new role with configurable permissions to control user access to links, media, users, and billing.

Instructions

Create a new role with permission settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesRole name
is_default_roleNoAuto-assign this role to new users
can_manage_linksNoCan manage tracking links
can_manage_mediaNoCan manage creatives and media groups
can_manage_usersNoCan manage users
publisher_accessNoPublisher access level
statistics_accessNoStatistics access level
can_manage_biddersNoCan manage bidders
can_manage_billingNoCan manage billing
can_manage_targetsNoCan manage targets
can_manage_ticketsNoCan manage tickets
can_manage_contractsNoCan manage contracts
can_manage_data_keysNoCan manage data keys
can_manage_product_dbNoCan manage product catalogs
can_manage_self_serveNoCan manage Self-Serve
publisher_access_listNoPublisher IDs for specific access
can_manage_programmaticNoCan manage programmatic
can_manage_admin_api_accessNoCan manage API keys
can_assign_campaigns_directlyNoCan assign campaigns directly
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. It only states 'create a new role' and doesn't mention side effects, required permissions, duplicate name handling, or response behavior—significant gaps for a mutating action.

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 a single concise sentence that front-loads the verb and resource. It contains no redundant or extraneous wording.

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?

Despite having 20 parameters and no output schema or annotations, the description provides no context about parameter relationships, default behavior, or success criteria. It is too minimal for the tool's complexity.

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 100% and each parameter has a clear description, so the description's generic 'permission settings' adds no meaning beyond the schema. Baseline 3 is appropriate since the schema already documents all parameters.

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 and resource: 'Create a new role'. It clearly indicates the tool's function and distinguishes it from sibling update/get/delete role tools through the 'create' action, though it doesn't explicitly name alternatives.

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?

No guidance is provided on when to use this tool vs alternatives, no prerequisites, and no exclusions. The intended use is only implied by the word 'create', which is insufficient for a 20-parameter administrative tool.

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