AudioAlpha

get_my_feed

Get a personalized feed based on the user's favorite assets and followed podcasts. Always uses the latest authoritative snapshot (is_latest). Returns snapshot_date and an array of assets, each containing: ticker, daily snapshot (sentiment, attention, consensus, momentum, summary), trading signals (with horizon, scenario, trigger, confidence, invalidating condition), and curated quotes (ranked with selection reason).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`version_info`	No	When true, include version metadata in the response: both version_num (the revision number) and version_label (a human-readable label like "eod_utc" for the initial end-of-day build, or "revised" when a later-indexed podcast triggered a regeneration). When false (the default), neither field is included. Note: the snapshot generation "status" field is ALWAYS returned regardless of this flag.
`snapshot_type`	No	Asset universe to draw the snapshot from. Currently only "crypto" is available; "tradfi" is reserved for a future release. Defaults to "crypto".	crypto
`episodes_lookback`	No	Number of recent episodes per followed podcast (max 10, default 3)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJun 23, 2026

changedInput schema / properties / version_info / description

Previous value: -"When true, include version metadata in the response: both version_num (the revision number) and version_label (a human-readable label like \"eod_utc\", \"backfill\", \"revised\"). When false (the default), neither field is included."New value: +"When true, include version metadata in the response: both version_num (the revision number) and version_label (a human-readable label like \"eod_utc\" for the initial end-of-day build, or \"revised\" when a later-indexed podcast triggered a regeneration). When false (the default), neither field is included. Note: the snapshot generation \"status\" field is ALWAYS returned regardless of this flag."

Changed1 schema field changedJun 15, 2026

changedInput schema / properties / version_info / description

Previous value: -"When true, include the human-readable version_label (e.g. \"eod_utc\", \"backfill\", \"revised\") alongside the always-present version_num in the response. Defaults to false."New value: +"When true, include version metadata in the response: both version_num (the revision number) and version_label (a human-readable label like \"eod_utc\", \"backfill\", \"revised\"). When false (the default), neither field is included."

Changed2 schema fields changedJun 12, 2026

addedInput schema / properties / snapshot_type

Added value: +{
+  "default": "crypto",
+  "description": "Asset universe to draw the snapshot from. Currently only \"crypto\" is available; \"tradfi\" is reserved for a future release. Defaults to \"crypto\".",
+  "enum": [
+    "crypto",
+    "tradfi"
+  ],
+  "type": "string"
+}

addedInput schema / properties / version_info

Added value: +{
+  "default": false,
+  "description": "When true, include the human-readable version_label (e.g. \"eod_utc\", \"backfill\", \"revised\") alongside the always-present version_num in the response. Defaults to false.",
+  "type": "boolean"
+}

First observedApr 13, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses a key behavioral trait: 'Always uses the latest authoritative snapshot (is_latest)', and it details the response structure. However, it does not mention potential edge cases, error conditions, or authentication/permissions. The description adds some value but is not rich behavioral context.

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?

The description is two sentences, front-loaded with the core purpose, then a structured list of returned fields. Every clause adds value and there is no redundant or filler content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description provides a comprehensive overview of the return payload, which is especially important since there is no output schema. It explains the feed's composition and the meaning of key fields. However, it lacks information about potential empty results or error handling, so it is slightly below maximum completeness.

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 coverage is 100%, with each parameter having a clear description. The tool description adds no additional parameter-level meaning beyond what the schema already provides, so it meets 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 clearly states the tool's purpose: 'Get a personalized feed based on the user's favorite assets and followed podcasts.' It uses a specific verb and resource, and the scope (personalized, based on favorites/followed podcasts) distinguishes it from siblings like get_market_snapshot or get_my_favorite_assets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the use case (personalized feed for the user), but it does not explicitly state when to use this tool vs alternatives, nor does it mention when not to use it. No alternative tools are referenced.

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

All AudioAlpha 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?