Skip to main content
Glama
Sign In
AdsMCP

AdsMCP

by skynes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ads_integration_list

Lists registered advertising integrations and built-in adapter capabilities with their configuration status, helping you verify which ad platforms are connected and ready to use.

Instructions

List registered integrations and built-in adapter capabilities/configuration status.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ads_integration_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral burden. It implies a read-only listing but does not disclose whether configuration values are sensitive, whether output is paginated, or what authentication or permissions are required.

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 definition is a single front-loaded sentence with no filler. It immediately states the operation and the objects being listed.

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 simple zero-parameter list tool, the description is adequate to understand the broad purpose. However, with no output schema and no annotations, it could say more about what the returned items contain, especially 'configuration status' and whether sensitive information is included.

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

Parameters4/5

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

The tool has zero parameters, so there is no parameter semantics to document. The baseline for zero-parameter tools is 4, and the description neither contradicts nor complicates that.

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 a specific verb ('List') and resource ('registered integrations and built-in adapter capabilities/configuration status'). It is clear enough to distinguish from write-oriented siblings like ads_integration_register, though it does not explicitly name an alternative.

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 implies you would call it to inspect integrations and adapter status, but it provides no explicit when-to-use or when-not-to-use guidance. With many sibling tools around integrations, planning, and platform configuration, this leaves routing to inference.

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