New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_viewers

Get unique viewer counts over time. USAGE: - By video: group_by=["video_id","video_title"] - By country: group_by=["country"] - Daily trend: interval="day" SORTING: Use sort_by (e.g., "day_desc"). Cannot sort by viewer count. Data limited to last 90 days.

SERVERZype Com SOURCEzype/zype-mcp
Low RISK CLASS
Category Read
Parameters 110 required
Recommended Allowedsee the rule below
Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/com-zype-mcp-server/get-viewers.md

What get_viewers does on Zype Com

AI agents call get_viewers to retrieve information from Zype Com without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
limit number — Max results to return (default: 200, max: 500)
offset number — Offset for pagination
country string — Filter by country code (e.g., "US", "GB", "CA")
sort_by string — Sort by field+direction. Default: day_desc. NOTE: Cannot sort by metric value - for top N by plays/views, fetch all and sort client-side.
group_by array — Group results by fields. Options: video_id, video_title, playlist_id, playlist_name, platform, consumer_id, country, domain, app_id, app_name, content_type
interval string — Time interval for grouping data (default: day)
platform string — Filter by platform (e.g., "ios", "android", "web", "roku")
video_id string — Filter by specific video ID
playlist_id string — Filter by playlist ID
start_date_gte string — Start date filter (YYYY-MM-DD). Max 90 days ago. Defaults to 2 weeks ago.
start_date_lte string — End date filter (YYYY-MM-DD). Defaults to today.

Parameters from the server's own tool schema.

Why get_viewers is rated Low

Even though get_viewers only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsHigh parameter count (11 properties)

Questions about get_viewers

What does the get_viewers tool do? +

Get unique viewer counts over time. USAGE: - By video: group_by=["video_id","video_title"] - By country: group_by=["country"] - Daily trend: interval="day" SORTING: Use sort_by (e.g., "day_desc"). Cannot sort by viewer count. Data limited to last 90 days. It is categorised as a Read tool in the Zype Com MCP Server, which means it retrieves data without modifying state.

What parameters does get_viewers accept? +

get_viewers accepts 11 parameters: limit, offset, country, sort_by, group_by, interval, platform, video_id, playlist_id, start_date_gte, start_date_lte. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_viewers? +

Register the Zype Com MCP server in PolicyLayer and add a rule for get_viewers: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Zype Com. Nothing to install.

What risk level is get_viewers? +

get_viewers is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_viewers? +

Yes. Add a rate_limit block to the get_viewers rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block get_viewers completely? +

Set action: deny in the PolicyLayer policy for get_viewers. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides get_viewers? +

get_viewers is provided by the Zype Com MCP server (zype/zype-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Zype Com, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Zype Com's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.