Skip to main content
Glama

get_audit

Retrieve audit logs for blocking, liking, favoriting, and notification records plus today's action usage counts by platform.

Instructions

查审计(拉黑 / 点赞 / 收藏 / 通知的每一条记录 + 今日各动作用量)。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo返回条数,默认 100
platformNo平台

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/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, and it does disclose what is returned (per-action records plus today's aggregate usage counts), which is genuinely useful for a tool lacking an output schema. However, it omits pagination behavior, ordering, time-window semantics, auth requirements, and whether the call is strictly read-only.

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?

A single compact sentence with the resource and the payload contents front-loaded, no filler. The parenthetical enumeration is dense but earns its place by defining scope.

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?

For a simple read tool with two optional parameters and no output schema, the description is adequately complete, covering the returned data categories in lieu of a documented return shape. Missing are ordering/pagination details and any caveat about the 'today' aggregation.

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%, with limit (default 100) and platform (enum bilibili/douyin) both documented in the schema, so the baseline is 3. The description adds no parameter-level meaning, and notably mentions a 'today' scope that has no corresponding parameter, leaving how limit interacts with the aggregate counts unclear.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (查/query) and resource (审计/audit) and enumerates exactly what the audit covers (block, like, collect, notification records plus today's per-action counts). It does not explicitly differentiate itself from siblings like get_blacklist, which returns only one of these record types, so the boundary must be inferred from the enumeration.

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?

Usage is only implied: an agent can infer this is the cross-action audit log versus get_blacklist with its single-action scope. There is no explicit when-to-use statement, no exclusion of alternatives, and no note on prerequisites.

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