Langfuse ACTION
List Observations
Retrieve a paginated list of observations from Langfuse with optional filters. See the documentation.
- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Langfuse account once, then configure and run List Observations 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: "langfuse-list-observations",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
langfuse: { authProvisionId: "apn_xxxxxxx" },
traceId: "Trace ID",
type: "Type",
},
})
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": "langfuse-list-observations",
"configured_props": {
"langfuse": { "authProvisionId": "apn_xxxxxxx" },
"traceId": "Trace ID",
"type": "Type"
}
}'// 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": "langfuse",
},
},
},
)
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: "langfuse-list-observations",
arguments: {
traceId: "Trace ID",
type: "Type",
},
})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 |
|---|---|---|
traceId Trace ID | string | The ID of a trace, for example trace-cm123abc456def789. Use the List Observations action to discover valid trace IDs. Optional |
type Type | string | Filter by observation type (e.g., "GENERATION", "SPAN", "EVENT", "AGENT", "TOOL", "CHAIN", "RETRIEVER", "EVALUATOR", "EMBEDDING", "GUARDRAIL"). Optional |
name Name | string | Filter observations by name. Optional |
fromStartTime From Start Time | string | Return observations that started at or after this timestamp. Use ISO 8601 format (e.g. 2024-01-01T00:00:00Z). Optional |
toStartTime To Start Time | string | Return observations that started before this timestamp. Use ISO 8601 format (e.g. 2024-12-31T23:59:59Z). Optional |
cursor Cursor | string | Base64-encoded cursor for pagination. Use the cursor from the previous response to get the next page. Optional |
limit Limit | integer | The number of observations to return per page. Min: 1, Max: 1000. 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
- langfuse-list-observations
- Version
- 0.0.2
- App
- Langfuse
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗