Skip to main content
Glama
Sign In
AdLoop: Google Ads, Reddit Ads & GA4

AdLoop: Google Ads, Reddit Ads & GA4

by kLOsk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Upload a conversion CSV

upload_conversion_csv
Read-only

Let the user upload a conversion CSV for an offline conversion upload.

Instructions

Let the user upload a conversion CSV for an offline conversion upload.

For the CSV behind draft_upload_call_conversions or draft_upload_enhanced_conversions_for_leads when the file is not on the machine running AdLoop, as on AdLoop Cloud. Apps that show AdLoop's cards display an upload card where the user drops the .csv file; the card then posts the upload id into the chat. Other apps on AdLoop Cloud get an upload link for the user (or a coding agent, with curl). The file holds personal data (phone numbers, emails), so it is kept for two hours at most and deleted as soon as a draft has read it. Returns the CSV uploads waiting to be used and how to add one.

Google Ads API: https://developers.google.com/google-ads/api/docs/start

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": "upload_conversion_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.33.1

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, it discloses the important operational facts: the file contains PII, is retained two hours at most, and is deleted as soon as a draft reads it, plus how the upload id or upload link flows back. The readOnlyHint/openWorldHint pair is not contradicted since the tool returns pending uploads rather than accepting file bytes, though the leading "Let the user upload" phrasing could momentarily read as a write.

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?

Purpose is front-loaded, but the body sprawls into UI narrative (upload card, upload id posted into chat, curl for a coding agent) that could be tightened. The trailing Google Ads API link adds little for an agent deciding how to call this tool.

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

Completeness4/5

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

For a zero-parameter tool with an output schema, this covers when to reach for it, how the user actually supplies the file, the PII/retention behaviour, and what comes back. The output schema carries the return-shape detail, so little is missing.

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 accepts zero parameters, so there is nothing for the schema to explain and the baseline is 4. The description correctly implies no arguments are needed and explains that the user supplies the file through a card or link.

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?

It states a specific verb and resource ("upload a conversion CSV for an offline conversion upload") and names the exact sibling drafts it feeds. The only friction is that the tool itself takes no input and returns pending uploads, so the name/title read as a write action while the actual behaviour is closer to a read/instruction tool.

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 explicitly scopes use to the case where the CSV is not on the machine running AdLoop (as on AdLoop Cloud) and ties it to draft_upload_call_conversions and draft_upload_enhanced_conversions_for_leads. It doesn't state an explicit when-not to use, but the branch conditions for cards vs. upload link are clear.

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