Skip to main content
Glama

Ads Manager by AdKit: Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads

by io.github.adkit
OverviewDiscussionsAdmin

adkit_upload_file

Upload one file to Meta, Google, TikTok, LinkedIn, X, ChatGPT Ads, or Studio from files, a public HTTPS URL, or a completed temporary upload. X and ChatGPT Ads currently support images. Use files when the client supports file inputs. Otherwise, use source for a public URL or completed temporary upload. Base64 payloads are not accepted. Report upload failures with adkit_feedback.

Input Schema

NameRequiredDescriptionDefault
filesNoSelect one file using the client instructions for this input. The client supplies download_url and file_id to AdKit. Do not invent these values. Use source if the client cannot pass files.
actionYesUse "upload" with files or source. Use "request_upload_url" when neither a client file input nor a public URL is available. Send the bytes to the returned upload URL before using its uploadId.
sourceNoOne public URL or completed temporary upload. Do not use together with files.
filenameNoFilename for request_upload_url.
accountIdNoAd account for Meta, Google, TikTok, LinkedIn, X, or ChatGPT Ads. May be omitted when AdKit can resolve one account.
projectIdNoRequired. Get from adkit_projects. Auto-resolves only for single-project users.
sizeBytesNoOptional exact file size for request_upload_url.
contentTypeNoMIME type for request_upload_url, for example image/png or video/mp4.
destinationNoRequired for upload. The platform or Studio library that should receive the file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"Use \"upload\" when the file is already attached, at a public URL, or in a completed temporary upload. Use \"request_upload_url\" only when the client cannot pass the file."New value: +"Use \"upload\" with files or source. Use \"request_upload_url\" when neither a client file input nor a public URL is available. Send the bytes to the returned upload URL before using its uploadId."
    • changedInput schema / properties / files / description
      Previous value: -"File supplied automatically by a host that supports MCP attachments. Never construct this field."New value: +"Select one file using the client instructions for this input. The client supplies download_url and file_id to AdKit. Do not invent these values. Use source if the client cannot pass files."
    • changedInput schema / properties / source / description
      Previous value: -"One public URL or completed temporary upload. Do not use when the host supplied a file."New value: +"One public URL or completed temporary upload. Do not use together with files."
  2. Changed2 schema fields changed
    • changedInput schema / properties / accountId / description
      Previous value: -"Ad account for Meta, Google, TikTok, LinkedIn, or X. May be omitted when AdKit can resolve one account."New value: +"Ad account for Meta, Google, TikTok, LinkedIn, X, or ChatGPT Ads. May be omitted when AdKit can resolve one account."
    • changedInput schema / properties / destination / enum
      Previous value: -[
-  "meta",
-  "google",
-  "tiktok",
-  "linkedin",
-  "x",
-  "studio"
-]New value: +[
+  "meta",
+  "google",
+  "tiktok",
+  "linkedin",
+  "x",
+  "chatgpt",
+  "studio"
+]
  3. First observed

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already disclose that this is a non-read-only, open-world, non-idempotent, non-destructive operation. The description adds useful behavioral constraints beyond the annotations: exactly one file, no base64 payloads, platform-specific image support, and the request_upload_url byte-upload workflow.

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 description is front-loaded with the core action and then efficiently covers source selection, platform limitations, and failure reporting. Every sentence provides actionable guidance with no repetition of schema text.

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

Completeness5/5

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

For a nine-parameter tool with nested objects and no output schema, the description covers the key workflow: destination platforms, accepted sources, the temporary upload fallback, the base64 restriction, and failure reporting. The schema supplies the remaining parameter detail.

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?

Schema description coverage is 100%, so the schema carries most parameter documentation. The description still adds meaningful semantics by clarifying the exclusive files-vs-source choice, when request_upload_url applies, and that base64 payloads are rejected.

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 states a specific verb and resource: upload one file to named ad platforms or Studio. It distinguishes supported source modes and platform-specific image limitations, so an agent can identify exactly what the tool does without opening the schema.

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

Usage Guidelines5/5

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

It explicitly says to use files when the client supports file inputs, otherwise use source for a public HTTPS URL or completed temporary upload, and reserves request_upload_url for when neither is available. It also names a sibling tool, adkit_feedback, for reporting failures.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Ads Manager by AdKit: Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources