How do I distinguish Zhihu question, answer and article IDs?
How do I distinguish Zhihu question, answer and article IDs? Follow concrete contracts, examples and reviewable steps using Zhihu.
Copy the agent prompt manually
Answer
Start by inspecting the contracts and local samples for Zhihu question detail, Zhihu answer detail, Zhihu article detail. Establish the input for zhihu.questions.get, then check whether its post object contains the fields your task needs.
Treat identifiers as typed values: content, account, comment and share-link identifiers are not interchangeable. Preserve the original string instead of converting large IDs to JavaScript numbers, and submit only fields explicitly defined by the contract.
Relevant contracts
| Capability | Object | Shape | Pagination |
|---|---|---|---|
| zhihu.questions.get | Post | item | No cursor |
| zhihu.answers.get | Post | item | No cursor |
| zhihu.articles.get | 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.
- GET: supply exactly one of id / url.
| Method | Field | Type | Requirement | Meaning | Enum or bound | Example |
|---|---|---|---|---|---|---|
| GET | id | string | Optional / conditional | Question ID, a string of digits | — | "55043447" |
| GET | url | string | Optional / conditional | Web link to the question | — | — |
| 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": "zhihu.questions.get",
"method": "GET",
"params": {
"id": "55043447"
}
}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 ↗