Skip to main content
Glama
kadam-official

@kadam-net/mcp-server

Official

kadam_adv_list_campaign_folders

Read-only

Retrieve a paginated list of advertiser campaign folders, with optional search by name.

Instructions

List advertiser campaign folders with pagination. Optional search by name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
perPageNo
searchQueryNo
Behavior3/5

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

Annotations already declare readOnlyHint=true. The description adds pagination and optional search context but does not disclose additional behavioral traits such as data freshness, access limitations, or rate limits.

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?

A single sentence that is efficient and front-loaded with the main purpose. No wasted words.

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 output schema and no parameter descriptions, the description fails to explain what a campaign folder is, how pagination works, or what the return data looks like, leaving gaps for new users.

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 coverage is 0%, so description must compensate. It mentions 'pagination' and 'search by name' but does not explain the page/perPage parameters or the searchQuery format, adding minimal semantic value.

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

Purpose5/5

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

The description uses the verb 'list' and specific resource 'advertiser campaign folders', clearly distinguishing from sibling tools like create or update campaign folders and from list_campaigns. It also mentions pagination and search features.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for listing campaign folders but does not explicitly state when to use or not use this tool versus alternatives, nor does it provide guidance on pagination or search behavior.

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/kadam-official/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server