Skip to main content
Glama
Sign In
KamyarTaher

@attrkit/mcp

by KamyarTaher
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update an ad-network integration

update_integration

Rotate credentials or enable/disable an integration. Update Meta/TikTok delivery scope and renewal events without changing its credentials or status.

Instructions

Rotate credentials or enable/disable an integration. set_delivery_options changes delivery_scope, renewal_event or both on a Meta or TikTok integration, in any status, without touching its credential or status; give at least one of the two.

Input Schema

NameRequiredDescriptionDefault
actionYes
ownersNo
credentialNo
connection_idYes
renewal_eventNoHow a renewal reaches Meta website and TikTok web events. purchase (the API's default): as Purchase with its price and currency. custom: as the custom event subscription_renewed with its price and currency, so Purchase counts one-time purchases only. App events are unchanged. A Google integration refuses custom.
delivery_scopeNoWhich events a Meta or TikTok integration sends. all (the API's default): the events of every install with measurement consent, organic ones included. attributed: send only events of installs AttriKit attributes to this connection's network (click ID, link token, or device match at or above the delivery floor); others are suppressed with attributed_only_suppressed. Meta and TikTok only: a Google integration refuses attributed.
idempotency_keyNoStable retry key for this exact mutation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare the mutation and safety profile, and the description adds useful behavior for set_delivery_options: it works in any status and does not touch credential or status. However, it does not explain side effects or requirements for rotate/disable/enable, nor does it mention idempotency behavior beyond the schema field.

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?

Two sentences, front-loaded, with no wasted wording. The action scope is stated first, followed by the important set_delivery_options constraint.

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

Completeness3/5

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

For a seven-parameter nested mutation tool with no output schema, the description covers the main action semantics and a key conditional requirement. It remains incomplete because the nested owners parameter and several action-specific details are undocumented.

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 schema description coverage is low at 43%, so the description needs to compensate. It adds meaningful cross-parameter guidance for set_delivery_options and maps rotate to credentials, but it leaves owners and connection_id unexplained and only partially covers credential semantics.

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 states specific verbs and resources: rotating credentials, enabling/disabling an integration, and changing delivery options. It clearly covers the tool's action scope, though it does not explicitly distinguish itself from sibling tools such as create_integration, delete_integration, or rotate_publishable_key.

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?

It gives clear usage context for set_delivery_options, including supported networks (Meta/TikTok), availability in any status, and the requirement to supply at least one of delivery_scope or renewal_event. It does not explicitly name alternatives or when-not-to-use cases for rotate/enable/disable.

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

Deploy Server

Other Tools