call-actor and get-actor-run fetch the Actor run object, which includes usageTotalUsd/usageUsd from the Apify API, but these are only attached to the MCP _meta field (com.apify/ActorRun), never to structuredContent. Most MCP clients (and the model) only see structuredContent, so the run cost is effectively invisible after calling an Actor.
get-actor-run-list already puts usageTotalUsd directly in structuredContent per item (actorRunListItemSchema), so the three tools are inconsistent.
Verified locally via mcpc @stdio tools-call call-actor: the raw response has
"_meta": { "com.apify/ActorRun": { "usageTotalUsd": 0.00005 } }
but structuredContent.stats only contains runTimeSecs, computeUnits, memMaxBytes — no cost.
Affected: call-actor, get-actor-run (both default and widget response variants).
call-actorandget-actor-runfetch the Actor run object, which includesusageTotalUsd/usageUsdfrom the Apify API, but these are only attached to the MCP_metafield (com.apify/ActorRun), never tostructuredContent. Most MCP clients (and the model) only seestructuredContent, so the run cost is effectively invisible after calling an Actor.get-actor-run-listalready putsusageTotalUsddirectly instructuredContentper item (actorRunListItemSchema), so the three tools are inconsistent.Verified locally via
mcpc @stdio tools-call call-actor: the raw response hasbut
structuredContent.statsonly containsrunTimeSecs,computeUnits,memMaxBytes— no cost.Affected:
call-actor,get-actor-run(both default and widget response variants).