assets_refresh_all
Queue an asset snapshot refresh
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| message | No | ||
| retryable | No | ||
| support_ref | No |
Queue an asset snapshot refresh
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| message | No | ||
| retryable | No | ||
| support_ref | No |
Changes observed during successful MCP inspections.
Input schema / properties / connection_contextRemoved value: -{
- "pattern": "^mctx_v1_[0-9a-f]{64}$",
- "type": "string"
-}Output schema / else / then / properties / categoryAdded value: +{
+ "type": "string"
+}Output schema / else / then / properties / expectedAdded value: +{
+ "type": "boolean"
+}Output schema / else / then / properties / failure_kindAdded value: +{
+ "type": "string"
+}Output schema / else / then / properties / responsibility_hintAdded value: +{
+ "type": "string"
+}Output schema / else / then / properties / routeAdded value: +{
+ "type": "string"
+}Output schema / else / then / properties / user_visibleAdded value: +{
+ "type": "boolean"
+}Input schema / properties / connection_contextAdded value: +{
+ "pattern": "^mctx_v1_[0-9a-f]{64}$",
+ "type": "string"
+}Output schema / $defsAdded value: +{
+ "s0": {
+ "properties": {
+ "count": {
+ "type": "integer"
+ },
+ "has_more": {
+ "type": "boolean"
+ },
+ "items": {
+ "items": {
+ "properties": {
+ "id": {
+ "type": "string"
+ },
+ "name": {
+ "type": [
+ "null",
+ "string"
+ ]
+ }
+ },
+ "required": [
+ "id"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "count",
+ "items",
+ "has_more"
+ ],
+ "type": "object"
+ },
+ "s3": {
+ "properties": {
+ "status": {
+ "enum": [
+ "requires_validation",
+ "awaiting_assets",
+ "blocked"
+ ],
+ "type": "string"
+ },
+ "summary": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "status",
+ "summary"
+ ],
+ "type": "object"
+ }
+}Output schema / else / else / properties / created_atAdded value: +{
+ "type": [
+ "null",
+ "string"
+ ]
+}Output schema / else / else / properties / finished_atAdded value: +{
+ "type": [
+ "null",
+ "string"
+ ]
+}Output schema / else / else / properties / launch_readinessAdded value: +{
+ "$ref": "#/$defs/s3"
+}Output schema / else / else / properties / refresh_summaryAdded value: +{
+ "properties": {
+ "failed_connections": {
+ "items": {
+ "properties": {
+ "label": {
+ "type": "string"
+ },
+ "reason": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "label",
+ "reason"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "failed_connections_count": {
+ "type": "integer"
+ },
+ "failed_connections_has_more": {
+ "type": "boolean"
+ },
+ "launch_readiness": {
+ "$ref": "#/$defs/s3"
+ },
+ "observed_at": {
+ "type": [
+ "null",
+ "string"
+ ]
+ },
+ "routing_errors": {
+ "type": "integer"
+ },
+ "scope": {
+ "enum": [
+ "tenant",
+ "fb_user"
+ ],
+ "type": "string"
+ },
+ "updated_assets": {
+ "properties": {
+ "ad_accounts": {
+ "$ref": "#/$defs/s0"
+ },
+ "businesses": {
+ "$ref": "#/$defs/s0"
+ },
+ "pages": {
+ "$ref": "#/$defs/s0"
+ }
+ },
+ "required": [
+ "ad_accounts",
+ "pages",
+ "businesses"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "observed_at",
+ "scope",
+ "updated_assets",
+ "failed_connections",
+ "launch_readiness"
+ ],
+ "type": [
+ "null",
+ "object"
+ ]
+}Output schema / else / else / properties / requested_scopeAdded value: +{
+ "enum": [
+ "tenant",
+ "fb_user"
+ ],
+ "type": "string"
+}Output schema / else / else / properties / started_atAdded value: +{
+ "type": [
+ "null",
+ "string"
+ ]
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare this is a non-read-only, non-destructive, closed-world operation, so the safety profile is covered. The description adds the useful nuance that the work is queued (asynchronous) rather than synchronous, but says nothing about scope of the refresh, cost, whether existing snapshots are replaced, or how completion is observed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single five-word sentence with the key verb and object front-loaded and no filler. Its brevity is a virtue here, since the tool takes no arguments.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists so return values need not be described, and annotations cover the mutation profile. However, for a fire-and-forget bulk refresh, the definition never says what 'all' covers, whether it applies per connection or globally, or how it interacts with assets_refresh_ad_account — meaningful gaps an agent would want filled.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has zero parameters, which is the baseline-4 case; there is nothing about parameters the description could or should explain. The schema's emptiness is consistent with the 'refresh all' framing.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Specific verb ('Queue') plus a specific resource ('asset snapshot refresh'), so the agent knows it enqueues rather than performs the refresh. It does not explicitly distinguish itself from the sibling assets_refresh_ad_account, leaving the 'all vs. one account' scope to be inferred from the name.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no statement of when to use this tool versus assets_refresh_ad_account or assets_lookup_business_links, nor any precondition such as needing a connection first. The only hint of applicability is the word 'all' embedded in the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.