How To Make Money On Snapchat

calculate_payout_timeline

Read-onlyIdempotent

CALCULATION. Use this when you need a date-by-date timeline of Snap's payout steps from a credited date: Pending to Available, the cash-out minimum, taxpayer verification, and the earliest day cash can reach the Payout Portal. Ranges stay ranges when the source gives a range. This is an estimate, not a promise. Do not use it to score eligibility (check_eligibility) or to list every rule (get_monetization_requirements).

Input Schema

Name	Required	Description
`amount_usd`	No	Available balance in USD, supplied by the caller. Omitted when unknown. Compared with the cash-out minimum from the rules database. Not a Snap pay rate.
`credited_date`	Yes	The day the reward appeared in All Activity, which is when Snap starts the pending clock. YYYY-MM-DD.
`tax_info_verified`	No	True when the caller says taxpayer verification is already finished. False when it is not. Omit when unknown. This service does not check a Snap account.

Output Schema

Name	Required	Description
`tool`	Yes
`facts`	Yes
`steps`	Yes
`notice`	Yes	Non-affiliation notice included in every response.
`caveats`	Yes
`sources`	Yes
`warnings`	No	Plain strings. Omitted when empty.
`amount_usd`	Yes
`api_version`	Yes
`generated_at`	Yes
`credited_date`	Yes
`meets_minimum`	Yes	True when amount_usd meets the cash-out minimum. False when it does not. Null when amount_usd was omitted.
`shortfall_usd`	Yes	How far amount_usd is under the cash-out minimum. 0 when the minimum is met. Null when amount_usd was omitted.
`data_freshness`	Yes
`recommendations`	Yes
`tax_info_verified`	Yes
`estimate_disclaimer`	Yes
`cash_out_minimum_usd`	Yes	The cash-out minimum copied from the rules database.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 31, 2026

changedOutput schema / allOf

Previous value: -[
-  {
-    "description": "Fields present in every successful tool output.",
-    "properties": {
-      "api_version": {
-        "const": "v1"
-      },
-      "data_freshness": {
-        "additionalProperties": false,
-        "properties": {
-          "generated_at": {
-            "format": "date-time",
-            "type": "string"
-          },
-          "newest_last_checked_at": {
-            "description": "Latest last_checked_at among rules in this response. Omitted when none of those rules have an unchanged-source check. Does not replace newest_verified_at.",
-            "format": "date-time",
-            "type": "string"
-          },
-          "newest_verified_at": {
-            "format": "date",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "oldest_last_checked_at": {
-            "description": "Earliest last_checked_at among rules in this response. Omitted when none of those rules have an unchanged-source check. Does not replace oldest_verified_at.",
-            "format": "date-time",
-            "type": "string"
-          },
-          "oldest_verified_at": {
-            "format": "date",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "policy": {
-            "description": "Human-readable freshness policy, e.g. 'Sources are re-checked daily; a rule is listed as stale when the later of verified_at and last_checked_at is more than 7 days before the response date.'",
-            "type": "string"
-          },
-          "rules_db_version": {
-            "description": "Monotonic version of the published rules set. Pattern YYYY-MM-DD.n",
-            "pattern": "^[0-9]{4}-[0-9]{2}-[0-9]{2}\\.[0-9]+$",
-            "type": "string"
-          },
-          "stale_rule_ids": {
-            "description": "Rules in this response whose later of verified_at and last_checked_at is older than the staleness window stated in `policy`. A missing last_checked_at does not count.",
-            "items": {
-              "maxLength": 120,
-              "pattern": "^[a-z0-9_]+(\\.[a-z0-9_]+)+$",
-              "type": "string"
-            },
-            "type": "array"
-          }
-        },
-        "required": [
-          "rules_db_version",
-          "generated_at",
-          "oldest_verified_at",
-          "newest_verified_at",
-          "stale_rule_ids",
-          "policy"
-        ],
-        "type": "object"
-      },
-      "generated_at": {
-        "format": "date-time",
-        "type": "string"
-      },
-      "notice": {
-        "const": "HowToMakeMoneyOnSnapchat.com is an independent third party and is not affiliated with, endorsed by, or sponsored by Snap Inc. Snapchat is a trademark of Snap Inc.",
-        "description": "Non-affiliation notice included in every response.",
-        "type": "string"
-      },
-      "sources": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "last_checked_at": {
-              "description": "ISO-8601 timestamp of the latest automated check that found this source's official text unchanged. Omitted when no such check is recorded. Does not replace verified_at.",
-              "format": "date-time",
-              "type": "string"
-            },
-            "publisher": {
-              "type": "string"
-            },
-            "supports_rule_ids": {
-              "items": {
-                "maxLength": 120,
-                "pattern": "^[a-z0-9_]+(\\.[a-z0-9_]+)+$",
-                "type": "string"
-              },
-              "type": "array"
-            },
-            "title": {
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "url": {
-              "format": "uri",
-              "type": "string"
-            },
-            "verified_at": {
-              "format": "date",
-              "type": "string"
-            }
-          },
-          "required": [
-            "url",
-            "publisher",
-            "verified_at",
-            "supports_rule_ids"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "tool": {
-        "type": "string"
-      },
-      "warnings": {
-        "description": "Plain strings. Omitted when empty. Calculation tools add a string when followers is 0 and view_time_hours_28d or spotlight_view_time_hours_28d is above 0, and when view_time_hours_28d exceeds 28 days × 24 hours × followers × 0.5. Those warnings say the figure is unusually high for your follower count, please check for a typo, and that view time can come from non-followers. They are never an error. FACT GET aliases append ignored query parameter notices to this same array. Spotlight hours above total view hours are HTTP 400 VALUE_INCONSISTENT rather than a warning.",
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "tool",
-      "api_version",
-      "notice",
-      "generated_at",
-      "sources",
-      "data_freshness"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "description": "Fields present in every successful tool output.",
+    "properties": {
+      "api_version": {
+        "const": "v1"
+      },
+      "data_freshness": {
+        "additionalProperties": false,
+        "properties": {
+          "generated_at": {
+            "format": "date-time",
+            "type": "string"
+          },
+          "newest_last_checked_at": {
+            "description": "Latest last_checked_at among rules in this response that have an unchanged-source check. Omitted when none do. Does not mean every rule was checked. Does not replace newest_verified_at.",
+            "format": "date-time",
+            "type": "string"
+          },
+          "newest_verified_at": {
+            "format": "date",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "oldest_last_checked_at": {
+            "description": "Earliest last_checked_at among rules in this response. Omitted unless every rule in this response has an unchanged-source check, so a rule with no check is not hidden. Does not replace oldest_verified_at.",
+            "format": "date-time",
+            "type": "string"
+          },
+          "oldest_verified_at": {
+            "format": "date",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "policy": {
+            "description": "Human-readable freshness policy, e.g. 'Sources are re-checked daily; a rule is listed as stale when the later of verified_at and last_checked_at is more than 7 days before the response date.'",
+            "type": "string"
+          },
+          "rules_db_version": {
+            "description": "Monotonic version of the published rules set. Pattern YYYY-MM-DD.n",
+            "pattern": "^[0-9]{4}-[0-9]{2}-[0-9]{2}\\.[0-9]+$",
+            "type": "string"
+          },
+          "stale_rule_ids": {
+            "description": "Rules in this response whose later of verified_at and last_checked_at is older than the staleness window stated in `policy`. A missing last_checked_at does not count.",
+            "items": {
+              "maxLength": 120,
+              "pattern": "^[a-z0-9_]+(\\.[a-z0-9_]+)+$",
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "rules_db_version",
+          "generated_at",
+          "oldest_verified_at",
+          "newest_verified_at",
+          "stale_rule_ids",
+          "policy"
+        ],
+        "type": "object"
+      },
+      "generated_at": {
+        "format": "date-time",
+        "type": "string"
+      },
+      "notice": {
+        "const": "HowToMakeMoneyOnSnapchat.com is an independent third party and is not affiliated with, endorsed by, or sponsored by Snap Inc. Snapchat is a trademark of Snap Inc.",
+        "description": "Non-affiliation notice included in every response.",
+        "type": "string"
+      },
+      "sources": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "last_checked_at": {
+              "description": "ISO-8601 timestamp of the latest automated check that found this source's official text unchanged. Omitted when no such check is recorded. Does not replace verified_at.",
+              "format": "date-time",
+              "type": "string"
+            },
+            "publisher": {
+              "type": "string"
+            },
+            "supports_rule_ids": {
+              "items": {
+                "maxLength": 120,
+                "pattern": "^[a-z0-9_]+(\\.[a-z0-9_]+)+$",
+                "type": "string"
+              },
+              "type": "array"
+            },
+            "title": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "url": {
+              "format": "uri",
+              "type": "string"
+            },
+            "verified_at": {
+              "format": "date",
+              "type": "string"
+            }
+          },
+          "required": [
+            "url",
+            "publisher",
+            "verified_at",
+            "supports_rule_ids"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "tool": {
+        "type": "string"
+      },
+      "warnings": {
+        "description": "Plain strings. Omitted when empty. Calculation tools add a string when followers is 0 and view_time_hours_28d or spotlight_view_time_hours_28d is above 0, and when view_time_hours_28d exceeds 28 days × 24 hours × followers × 0.5. Those warnings say the figure is unusually high for your follower count, please check for a typo, and that view time can come from non-followers. They are never an error. FACT GET aliases append ignored query parameter notices to this same array. Spotlight hours above total view hours are HTTP 400 VALUE_INCONSISTENT rather than a warning.",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "tool",
+      "api_version",
+      "notice",
+      "generated_at",
+      "sources",
+      "data_freshness"
+    ],
+    "type": "object"
+  }
+]

changedOutput schema / properties / data_freshness / properties / newest_last_checked_at / description

Previous value: -"Latest last_checked_at among rules in this response. Omitted when none of those rules have an unchanged-source check. Does not replace newest_verified_at."New value: +"Latest last_checked_at among rules in this response that have an unchanged-source check. Omitted when none do. Does not mean every rule was checked. Does not replace newest_verified_at."

changedOutput schema / properties / data_freshness / properties / oldest_last_checked_at / description

Previous value: -"Earliest last_checked_at among rules in this response. Omitted when none of those rules have an unchanged-source check. Does not replace oldest_verified_at."New value: +"Earliest last_checked_at among rules in this response. Omitted unless every rule in this response has an unchanged-source check, so a rule with no check is not hidden. Does not replace oldest_verified_at."

AddedOct 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is not obliged to repeat them. It adds real context beyond them: 'Ranges stay ranges when the source gives a range' discloses output-shape behavior, and 'This is an estimate, not a promise' sets expectations about result reliability. The only small gap is that it does not say what happens if required context like credited_date is in the future or malformed.

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?

The description is front-loaded with the purpose, then the exclusions, then the validity caveat, with no filler sentences. The leading 'CALCULATION.' label is slightly redundant with the tool name and the schema description, which prevents a 5.

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?

An output schema exists, so return values need not be explained, and the annotations carry the safety profile. Given three well-documented parameters and low structural complexity, the description plus structured data cover everything an agent needs to call this tool correctly and interpret its estimate caveat.

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 credited_date, amount_usd, and tax_info_verified in detail, including omit-when-unknown semantics. The description mentions the same concepts (cash-out minimum, taxpayer verification) but adds no syntax, format, or edge-case guidance beyond what the schema provides, so the baseline 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?

It names a specific verb and resource ('date-by-date timeline of Snap's payout steps from a credited date') and enumerates the steps it covers: Pending to Available, cash-out minimum, taxpayer verification, and earliest cash arrival. It also explicitly separates itself from check_eligibility and get_monetization_requirements, so the agent can distinguish it from siblings without opening a schema.

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?

The description gives an explicit trigger ('Use this when you need a date-by-date timeline'), explicit exclusions ('Do not use it to score eligibility... or to list every rule'), and names the correct alternative for each excluded case. Nothing about when to select this tool is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All How To Make Money On Snapchat tools Inspect

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

Need Help?