Skip to main content
Glama
Sign In
microsoft-ads-mcp

microsoft-ads-mcp

by shinypebble
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

bulk_upload

Apply bulk CSV rows to your Microsoft Ads account, with polling until completion.

Instructions

Apply ready-made Bulk CSV rows to the account; polls to completion.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entity_records": "<entity_records>"
    },
    "name": "bulk_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_recordsYesBulk-file CSV rows (including the Format Version / Type header rows Microsoft expects). Returns the request status and result file URL.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations indicate readOnlyHint=false, so the description adds minimal extra behavioral context. It mentions polling but does not disclose details like whether it's synchronous, how long polling takes, what gets destroyed, or authorization needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that efficiently states the action and polling behavior without wasted words. It could be slightly improved by front-loading the purpose more prominently.

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?

Despite having an output schema, the description does not explain the polling mechanism, return format, or error states. For a bulk upload tool, this lacks completeness for an agent to fully understand the behavior.

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?

Schema description coverage is 100%, and the parameter description already explains the CSV rows and expected output. The tool description adds context about applying to the account but does not add meaning beyond 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 clearly states it applies ready-made Bulk CSV rows to the account and polls to completion, specifying the verb and resource. However, it does not differentiate from the sibling 'bulk_download' tool, which is for downloading.

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 when CSV rows are ready and the tool will poll to completion, but it does not explicitly state when to use this tool versus alternatives or provide exclusion criteria.

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