Skip to main content
Glama
Sign In
AdsMCP

AdsMCP

by skynes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ads_network_profile_list

Find opt-in networking profiles in the optional relay registry by kind or region to locate relevant advertising contacts.

Instructions

Find opt-in networking profiles in the optional relay registry.

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_network_profile_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
regionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden. 'Opt-in' and 'optional relay registry' weakly imply the result set is already filtered to consented entries, but nothing is said about pagination, result volume, permissions, or ordering — the caller cannot predict what comes back.

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?

It is a single front-loaded sentence with no waste, but it is under-specified rather than concise — the terseness comes at the cost of information an agent needs.

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?

With no annotations, no output schema, and two undocumented parameters, the description should do substantial work but instead supplies one vague sentence. A caller has no basis for choosing filter values or interpreting the returned profile list.

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

Parameters2/5

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

Schema description coverage is 0% and neither of the two optional parameters (kind, region) is mentioned in the description. An agent must guess the accepted values of 'kind' and the format of 'region' entirely, so the description adds essentially no parameter meaning.

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

Purpose3/5

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

The verb 'Find' plus resource 'networking profiles' does indicate a list/search operation, and 'opt-in' hints at a filter on the result set. However, 'optional relay registry' is undefined jargon that gives no clue what a networking profile actually is, and the description does not distinguish itself from nearby siblings such as ads_network_platform_list or ads_network_profile_publish.

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 statement of when to reach for this tool versus ads_network_platform_list, ads_network_inventory_list, or the publish counterparts. 'Opt-in' implies a scoping rule but no prerequisites, exclusions, or alternatives are given.

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