Moodle ACTION
Update a Course
Updates an existing course in Moodle, including name, summary, and visibility. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Moodle account once, then configure and run Update a Course 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: "moodle-update-course",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
moodle: { authProvisionId: "apn_xxxxxxx" },
courseId: "Course ID",
fullname: "Full Name",
},
})
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": "moodle-update-course",
"configured_props": {
"moodle": { "authProvisionId": "apn_xxxxxxx" },
"courseId": "Course ID",
"fullname": "Full Name"
}
}'// 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": "moodle",
},
},
},
)
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: "moodle-update-course",
arguments: {
courseId: "Course ID",
fullname: "Full Name",
},
})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 |
|---|---|---|
courseId Course ID | string | The ID of the course Required Dynamic |
fullname Full Name | string | The updated full name of the course Optional |
shortname Short Name | string | The updated short name of the course Optional |
summary Summary | string | The updated summary or description for the course Optional |
visible Visible | boolean | Whether the course should be visible to students Optional |
categoryId Category ID | string | Move the course to a different category by ID (for example, 42) Optional Dynamic |
startDate Start Date | integer | The updated course start date as a Unix timestamp in seconds (for example, 1714521600 for 2024-05-01T00:00:00Z) Optional |
endDate End Date | integer | The updated course end date as a Unix timestamp in seconds (for example, 1717113600 for 2024-05-31T00:00:00Z) 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
- moodle-update-course
- Version
- 0.0.1
- App
- Moodle
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗