PagerDuty ACTION
List Log Entries
List log entries (the audit trail of actions taken on an incident or across the account). When
incidentId is provided, scopes results to that incident's log entries. Otherwise returns account-wide log entries. Use List Incidents or Get Incident to find incident IDs. Time params use ISO 8601 with explicit UTC offset, e.g. 2026-06-02T15:00:00-07:00. Set isOverview: true to get only the most recent action per incident. See the documentation- Action
- Read only
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's PagerDuty account once, then configure and run List Log Entries from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "pagerduty-list-log-entries",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
pagerduty: { authProvisionId: "apn_xxxxxxx" },
incidentId: "Incident ID",
since: "Since",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "pagerduty-list-log-entries",
"configured_props": {
"pagerduty": { "authProvisionId": "apn_xxxxxxx" },
"incidentId": "Incident ID",
"since": "Since"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "pagerduty",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "pagerduty-list-log-entries",
arguments: {
incidentId: "Incident ID",
since: "Since",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
incidentId Incident ID | string | When provided, returns log entries for this incident only (e.g., PIJ12345678). Use List Incidents to find IDs. Leave empty for account-wide log entries. Optional |
since Since | string | Start of time range (ISO 8601 with UTC offset, e.g. 2026-06-02T15:00:00-07:00). Optional |
until Until | string | End of time range (ISO 8601 with UTC offset, e.g. 2026-06-02T15:00:00-07:00). Optional |
isOverview Overview Only | boolean | When true, returns only the most recent log entry for each incident. Optional |
limit Limit | integer | Maximum number of results to return (1–100). Default: 25. Optional |
offset Offset | integer | Pagination offset. Default: 0. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- pagerduty-list-log-entries
- Version
- 0.0.2
- App
- PagerDuty
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗