Skip to main content
Glama

x_api_get_posts_counts_all

Retrieve the total count of posts that match a given query. Use this read-only tool to obtain post count metrics for analysis and reporting.

Instructions

Get count of all Posts. Use when: Get count of all Posts. Do not use when: a more specific auth/configuration tool is required before the API call or you are only exploring; prefer x_schema_discovery or x_query_suggestion first. Risk: read-only. Required permissions and prerequisites: bearer token Environment-selection behavior: scopeTenantId plus exactly one of scopeUserId or scopeAccountId choose the Vault/Postgres tenant principal used for auth resolution. credentialKey selects a non-default stored credential profile when present. Parameter formats and constraints: query (query, string, required); start_time (query, string); end_time (query, string); since_id (query, unknown); until_id (query, unknown); next_token (query, unknown); pagination_token (query, unknown); granularity (query, string). Expected response shape: { ok, status, data: { method, path, url, status, contentType, authType, data } } Common failure conditions: missing scoped credentials in Vault, missing required API parameters, X API auth failures, rate limits, or unsupported multipart/body shape. Recommended prerequisite and follow-up tools: x_connection_info, x_schema_discovery, x_auth_get_scope_credentials, x_api_request. Safety warnings: This is read-only, but responses can still include sensitive account data depending on granted scopes. Example: {"name":"x_api_get_posts_counts_all","arguments":{"scopeTenantId":"default","scopeUserId":"default"}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
end_timeNo
since_idNo
until_idNo
next_tokenNo
start_timeNo
granularityNo
scopeUserIdNo
credentialKeyNo
scopeTenantIdNo
scopeAccountIdNo
authorizationKeyNo
pagination_tokenNo
preferredAuthTypeNo
Behavior5/5

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

Despite no annotations, the description discloses read-only risk, bearer token requirement, environment-selection behavior, expected response shape, common failure conditions, and safety warnings. This goes well beyond basic safety hints and gives the agent useful behavioral context for invoking the tool correctly.

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?

The description is structured into labeled sections and is information-dense, but the 'Use when' line repeats the first sentence and read-only is mentioned twice. Still, it earns its length given the tool complexity.

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

Completeness3/5

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

It provides response shape, failure conditions, prerequisites, an example, and safety notes, which is strong for a complex tool without an output schema. However, it misses parameter semantics and does not clarify the relationship with counts_recent, so some context is lacking.

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 0%, so the description must compensate. It lists several parameter names and types and explains scopeUserId/scopeTenantId/credentialKey selection, but it does not define the meaning of query, granularity, or the since_id/until_id/next_token/pagination_token fields, leaving significant gaps.

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?

The description opens with 'Get count of all Posts,' which is a clear verb+resource statement. However, it does not explicitly differentiate from sibling tool x_api_get_posts_counts_recent or clarify that 'all' refers to full-archive vs recent counts, leaving some ambiguity.

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

Usage Guidelines2/5

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

The 'Use when' line merely restates the purpose and provides no situational guidance. The 'Do not use when' gives generic advice to prefer x_schema_discovery or x_query_suggestion when exploring, but does not specify when to choose this tool over counts_recent or related search tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/LesterAJohn/X-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server