How should I read and interpret WeChat Channels play counts?
How should I read and interpret WeChat Channels play counts? Follow concrete contracts, examples and reviewable steps using WeChat Channels.
Copy the agent prompt manually
Answer
Start by inspecting the contracts and local samples for WeChat Channels video stats. Establish the input for wechat_channels.videos.metrics, then check whether its post object contains the fields your task needs.
Align the metric name, denominator, observation window and capture time first. Indices, reads, impressions, plays, engagement and cost are different measurements. A missing value means unavailable, not zero; likes cannot substitute for reads.
Relevant contracts
| Capability | Object | Shape | Pagination |
|---|---|---|---|
| wechat_channels.videos.metrics | Post | item | No cursor |
Input contract
Inspect meanings, examples and conditional rules for the selected method. view and fields control the response without changing the TEST unit price.
- Only send fields defined for this method; unknown fields are rejected before execution.
| Method | Field | Type | Requirement | Meaning | Enum or bound | Example |
|---|---|---|---|---|---|---|
| GET | id | string | Required | The video's ID, a string of digits: the id a video list or a video gives | — | "14940144898316503592" |
| GET | view | string | Optional / conditional | How much of each item: compact (the most used fields, long text cut short), standard, or full (adds `ext`). | ["compact","standard","full"] | — |
| GET | fields | array | Optional / conditional | Return only these fields of each item, by path (`author.name`). | maxItems: 64 | — |
Complete one verification
Run one local fixture for a listed capability and inspect the object structure. Then filter, classify or export according to the question. A local sample cannot replace evidence for a real-platform conclusion.
{
"capability": "wechat_channels.videos.metrics",
"method": "GET",
"params": {
"id": "14940144898316503592"
}
}Clear inputs. Inspectable output.
Each click runs a local fixture. Advanced JSON inputs are checked against the selected method. Editing does not execute a request.
Copying does not execute. CLI quote is read-only and needs a local customer TEST key. Configure MCP in demo mode first. GET and POST batches both return only fictional local fixtures.
Download contract example (no execution) ↗For TEST budgets, Key scopes or failure scenarios, open the account console. Customer sandbox ↗