Skip to main content
Glama
adbutler

AdButler MCP Server

Official
by adbutler

update_role

Update an existing role in AdButler, modifying its permissions, access levels, and other settings to keep user capabilities aligned with your advertising account.

Instructions

Update an existing role

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesRole ID
nameNoRole name
is_default_roleNoAuto-assign to new users
can_manage_linksNoCan manage tracking links
can_manage_mediaNoCan manage creatives
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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It merely says 'update an existing role' without mentioning whether fields are partially updated or reset, what permissions are required, what the response contains, or any side effects. This is a significant gap for a mutation tool.

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 with no wasted words. It is front-loaded and easy to parse. While it is minimal, it earns its place by stating the core action clearly without filler.

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's complexity (21 parameters, no output schema, no annotations), the description is far too incomplete. It does not explain update behavior, return values, prerequisites, or how this tool relates to role management workflows. The schema covers parameter names but not operational context.

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 covers 100% of the 21 parameters with descriptions, so the baseline is 3. The description adds no additional parameter meaning beyond the schema, such as update semantics or how omitted fields are treated. It does not compensate for or enhance the schema.

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 'Update an existing role' clearly states the action (update) and resource (role), and the word 'existing' distinguishes it from create_role. However, it is a minimal restatement of the tool name and adds no scope or detail beyond the action, so it falls short of a fully informative purpose statement.

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?

The description provides no guidance on when to use this tool versus alternatives such as get_role, create_role, or delete_role. It only implies that the role must already exist, but it does not mention prerequisites, related tools, or situations where this tool should or should not be used.

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