Skip to main content
Glama
ionos-cloud

IONOS CLOUD MCP Server

Official

list_activitylog_events

Query the IONOS CLOUD activity log to get a full audit trail of API requests for a contract, with filters for user, event types, and date range.

Instructions

Query the IONOS CLOUD activity log: full audit trail of API requests made against a contract (who did what, when, on which resource). Requires ACCESS_ACTIVITY_LOG privilege on the token. Defaults: last 7 days, limit 25, RequestStatusUpdate events excluded. Use user filter to narrow to a specific account. Use event_types to restrict to e.g. ['Error','RequestAccepted']. Maximum date range is 90 days — paginate or narrow the window for longer spans. Use list_activitylog_contracts first to look up the contract number if needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contractYesthe contract number whose activity log to query; reseller/partner users get IDs from list_activitylog_contracts, single-contract users read it from their JWT
date_startNoinclusive start date YYYY-MM-DD; defaults to 7 days ago when omitted
date_endNoinclusive end date YYYY-MM-DD; defaults to today when omitted; maximum range is 90 days
offsetNo0-based pagination offset
limitNomax events to return; defaults to 25; increase only when the user explicitly asks for bulk data
userNofilter by username (client-side); e.g. 'ionosctl-v6@cloud.ionos.com' — drastically reduces output when investigating a specific user
event_typesNofilter to these event types only (client-side); e.g. ['Error','RequestAccepted'] — omit Provision and RequestStatusUpdate to cut ~65% of typical log volume
include_status_updatesNoinclude RequestStatusUpdate events (default false); these are async provisioning echoes that account for ~55% of log volume and are rarely useful
Behavior5/5

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

No annotations provided, so description carries full burden. Discloses default behavior (7 days, limit 25, excluded event types), maximum range, and pagination advice. Also mentions privilege requirement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single paragraph, front-loaded with purpose, then requirements, defaults, and usage advice. Every sentence is meaningful and no redundant information.

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?

No output schema, but input is fully described along with behavior and prerequisites. Lacks mention of output structure or pagination response details, but for a list tool this is acceptable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds significant value: explains contract source, date range defaults, pagination offset, recommendation for limit increase, client-side filtering for user and event_types, and clarity on include_status_updates default and volume impact.

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

Purpose5/5

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

Clearly states 'Query the IONOS CLOUD activity log: full audit trail of API requests made against a contract (who did what, when, on which resource).' This is a specific verb+resource that distinguishes it from sibling list/get tools.

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

Usage Guidelines4/5

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

Provides explicit context: required privilege, defaults, maximum date range, and suggests using list_activitylog_contracts first for contract lookup. Does not explicitly state when not to use it, but the context is sufficient.

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/ionos-cloud/ionoscloud-mcp'

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