Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

meta_ads_images_upload_file

Upload local image files to Meta Ads and retrieve the image_hash needed for ad creative construction. Ideal for images stored on disk, with support for JPG, PNG, and GIF up to 30 MB.

Instructions

Uploads an image from a local file path to the Meta Ads account library. Returns the image_hash to reference in creative-construction tools. Mutating — the asset is persisted. Use this when the image lives on the agent's local disk; for public-URL uploads use meta_ads_creatives_upload_image instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional label stored with the uploaded asset. Used only for library organization.
reasonNoWhy this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.
file_pathYesPath to the image file on the agent's filesystem. Meta accepts JPG, PNG, and GIF up to 30 MB.
account_idNoMeta Ads account ID in the format 'act_XXXXXXXXXX' (e.g. 'act_1234567890'). Optional — falls back to META_ADS_ACCOUNT_ID from the configured credentials. The leading 'act_' prefix is required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.20.0
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Why this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.",
+  "maxLength": 500,
+  "type": "string"
+}
  2. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv0.9.12
  4. Removedv0.9.6
  5. Addedv0.9.2
  6. Removedv0.9.1
  7. Addedv1.0.5

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and it meets it: it explicitly warns 'Mutating — the asset is persisted' and tells the agent the meaningful return value (image_hash). This is enough for an agent to understand the side effect and downstream use, though it does not discuss idempotency or account authorization.

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?

Three tight sentences with no filler: action, return value, mutation flag, then the routing rule. The most important decision-relevant info is front-loaded.

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 mutating upload tool with no annotations and no output schema, the description covers the essential context: when to use it, what it does, that it persists, what it returns, and which sibling to use instead. The schema handles parameter specifics, so nothing an agent needs to invoke it correctly is missing.

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 the schema already documents file_path, name, reason, and account_id. The description adds the key conceptual framing (local file vs public URL) but does not add parameter-level details beyond the schema, which is acceptable at the baseline.

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 names a specific verb ('upload'), a specific resource ('image from a local file path to the Meta Ads account library'), and a concrete outcome ('returns the image_hash'). It also distinguishes this tool from the public-URL upload path, so an agent can identify it among many sibling tools without ambiguity.

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 states when to use this tool: when the image lives on the agent's local disk. It also names the alternative tool for public-URL uploads (meta_ads_creatives_upload_image), giving the agent a clear decision rule.

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