tasks_get_status
Poll task_ref; never retry unchanged writes
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| task_ref | No | ||
| response_mode | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| message | No | ||
| retryable | No | ||
| support_ref | No |
Poll task_ref; never retry unchanged writes
| Name | Required | Description | Default |
|---|---|---|---|
| task_ref | No | ||
| response_mode | No |
| Name | Required | Description | Default |
|---|---|---|---|
| message | No | ||
| retryable | No | ||
| support_ref | No |
Changes observed during successful MCP inspections.
Output schema / else / properties / workspace_refAdded value: +{
+ "description": "Opaque workspace comparison hint; not an authorization credential.",
+ "pattern": "^workspace_[0-9a-f]{32}$",
+ "type": "string"
+}Output schema / $defs / s10Added value: +{
+ "properties": {
+ "ads": {
+ "type": "integer"
+ },
+ "adsets": {
+ "type": "integer"
+ },
+ "auxiliary_writes": {
+ "type": "integer"
+ },
+ "campaigns": {
+ "type": "integer"
+ },
+ "creative_keys": {
+ "type": "integer"
+ }
+ },
+ "type": "object"
+}Output schema / $defs / sb / properties / adsRemoved value: -{
- "type": "integer"
-}Output schema / $defs / sb / properties / adsetsRemoved value: -{
- "type": "integer"
-}Output schema / $defs / sb / properties / auxiliary_writesRemoved value: -{
- "type": "integer"
-}Output schema / $defs / sb / properties / campaignsRemoved value: -{
- "type": "integer"
-}Output schema / $defs / sb / properties / countAdded value: +{
+ "type": "integer"
+}Output schema / $defs / sb / properties / creative_keysRemoved value: -{
- "type": "integer"
-}Output schema / $defs / sb / properties / has_moreAdded value: +{
+ "type": "boolean"
+}Output schema / $defs / sb / properties / itemsAdded value: +{
+ "items": {
+ "properties": {
+ "id": {
+ "type": "string"
+ },
+ "name": {
+ "type": [
+ "null",
+ "string"
+ ]
+ }
+ },
+ "required": [
+ "id"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+}Output schema / $defs / sb / requiredAdded value: +[
+ "count",
+ "items",
+ "has_more"
+]Output schema / $defs / seAdded value: +{
+ "properties": {
+ "status": {
+ "enum": [
+ "requires_validation",
+ "awaiting_assets",
+ "blocked"
+ ],
+ "type": "string"
+ },
+ "summary": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "status",
+ "summary"
+ ],
+ "type": "object"
+}Output schema / else / properties / result / properties / create_reconciliation / properties / created / $refPrevious value: -"#/$defs/sb"New value: +"#/$defs/s10"Output schema / else / properties / result / properties / create_reconciliation / properties / failed / $refPrevious value: -"#/$defs/sb"New value: +"#/$defs/s10"Output schema / else / properties / result / properties / create_reconciliation / properties / recovered / $refPrevious value: -"#/$defs/sb"New value: +"#/$defs/s10"Output schema / else / properties / result / properties / create_reconciliation / properties / requested / $refPrevious value: -"#/$defs/sb"New value: +"#/$defs/s10"Output schema / else / properties / result / properties / create_reconciliation / properties / unreconciled / $refPrevious value: -"#/$defs/sb"New value: +"#/$defs/s10"Output schema / else / properties / result / properties / created_atAdded value: +{
+ "type": [
+ "null",
+ "string"
+ ]
+}Output schema / else / properties / result / properties / finished_atAdded value: +{
+ "type": [
+ "null",
+ "string"
+ ]
+}Output schema / else / properties / result / properties / last_refreshed_atAdded value: +{
+ "type": [
+ "null",
+ "string"
+ ]
+}Output schema / else / properties / result / properties / launch_readinessAdded value: +{
+ "$ref": "#/$defs/se"
+}Output schema / else / properties / result / properties / refresh_scopeAdded value: +{
+ "enum": [
+ "tenant",
+ "fb_user"
+ ],
+ "type": "string"
+}Output schema / else / properties / result / 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/se"
+ },
+ "observed_at": {
+ "type": [
+ "null",
+ "string"
+ ]
+ },
+ "routing_errors": {
+ "type": "integer"
+ },
+ "scope": {
+ "enum": [
+ "tenant",
+ "fb_user"
+ ],
+ "type": "string"
+ },
+ "updated_assets": {
+ "properties": {
+ "ad_accounts": {
+ "$ref": "#/$defs/sb"
+ },
+ "businesses": {
+ "$ref": "#/$defs/sb"
+ },
+ "pages": {
+ "$ref": "#/$defs/sb"
+ }
+ },
+ "required": [
+ "ad_accounts",
+ "pages",
+ "businesses"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "observed_at",
+ "scope",
+ "updated_assets",
+ "failed_connections",
+ "launch_readiness"
+ ],
+ "type": [
+ "null",
+ "object"
+ ]
+}Output schema / else / properties / result / properties / requested_scopeAdded value: +{
+ "enum": [
+ "tenant",
+ "fb_user"
+ ],
+ "type": "string"
+}Output schema / else / properties / result / properties / started_atAdded value: +{
+ "type": [
+ "null",
+ "string"
+ ]
+}Output schema / else / properties / result / properties / task_refAdded value: +{
+ "type": "string"
+}Output schema / else / properties / result / properties / task_statusAdded value: +{
+ "type": "string"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false). The description adds that this is a polling operation and warns against retrying unchanged writes, which is genuine behavioral context, but it is too terse to explain polling cadence, termination, or what makes a write 'unchanged'.
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?
Seven words is compact and front-loads the action, but it is under-specified rather than genuinely concise. The second clause is ambiguous enough that it costs more agent comprehension than it saves.
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, but for a tool sitting in a dense cluster of task_* siblings with 0% schema coverage, the definition omits tool selection, parameter meaning, and polling behavior. It is not complete enough for reliable invocation.
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?
Schema description coverage is 0%, so the description carries the full burden. It names task_ref but adds no meaning (format, origin, or whether it is required), and it completely omits response_mode and its compact/standard enum values.
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?
The verb 'Poll' with the explicit 'task_ref' resource makes the core action clear: repeatedly query a task reference. However, it does not distinguish itself from siblings like tasks_latest, tasks_list, or tasks_get_create_detail, so an agent must still infer which task-query tool applies.
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?
The clause 'never retry unchanged writes' is a usage hint, but it is cryptic and never names the alternatives (tasks_latest, tasks_list, tasks_get_create_detail) or the conditions that select this tool. No when-not guidance is present.
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.