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

Beta. Upload one file to Meta, Google, TikTok, LinkedIn, X, ChatGPT Ads, or Studio from a host-provided attachment, public HTTPS URL, or completed temporary upload. X and ChatGPT Ads currently support images. When no attachment or public URL exists, a requested upload URL fills the same role. Base64 payloads and local file paths are not accepted. Report upload failures with adkit_feedback.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesNoFile supplied automatically by a host that supports MCP attachments. Never construct this field.
actionYesUse "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.
sourceNoOne public URL or completed temporary upload. Do not use when the host supplied a file.
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. 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"
+]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds valuable non-obvious constraints: beta status, which source types are accepted, that base64 and local paths are rejected, and that X and ChatGPT Ads are image-only. It stops short of describing success output 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.

Conciseness4/5

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

Front-loaded with the beta flag and core action, then constraints, then failure routing. Dense and largely waste-free, though the middle sentence about upload URLs is slightly convoluted.

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 9-parameter mutation tool with nested objects and no output schema, the description covers sources, platform restrictions, rejection cases, and failure handling. It omits what a successful call returns (e.g., file id) and any permission requirements, which are minor gaps.

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%, so every parameter is already documented in the schema, including the action semantics and the source object. The description restates the accepted source forms but adds no syntax or format detail beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb and resource ('Upload one file') plus the full set of destinations, so an agent can immediately distinguish this from adkit_library, adkit_studio, or adkit_manage. The scope constraint ('one file') is explicit.

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?

Clearly explains the two action modes ('upload' when the file is attached/URL/temporary upload; 'request_upload_url' only when the client cannot pass the file) and the fallback when no attachment or URL exists. It also routes failures to adkit_feedback, but gives no explicit guidance on when NOT to use this tool versus siblings.

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