Connect Claude & ChatGPT to Content Snare

20 tools for Content Snare

These tools are switched on when you connect. You can switch any of them off, or require your approval before it runs.

• approve_requestVisible to othersApprove every submitted field in a request (`request_id`). The client can see the approval.
• approve_request_pageVisible to othersApprove every submitted field on one request page (`page_id`). The client can see the approval.
• approve_request_sectionVisible to othersApprove every submitted field in one section (`section_id`). The client can see the approval.
• create_clientChanges dataCreate a client with `full_name` and `email`, plus optional phone, language and companies. Search first to avoid duplicates.
• create_requestChanges dataCreate a document request with a `name`, optional client_id, due date (yyyy-mm-dd), status (draft or published) and template. Publishing sends the request to the client.
• delete_clientDeletesPermanently delete a client by `customer_id`. This cannot be undone.
• get_clientGet one client by `customer_id`, with contact details and companies.
• get_current_userGet the Content Snare team member you are connected as, including name, email and role.
• get_requestGet one document request by `request_id`, with its client, status, due date and progress.
• get_request_pageGet one page of a request by `page_id`, including its sections, fields and client answers.
• list_foldersList the folders requests are grouped into, with paging.
• list_request_templatesList request templates you can base a new request on, optionally filtered by source.
• review_fieldVisible to othersApprove or reject one field's answer by `field_id`: set status to approved, or redo with a rejection_comment telling the client what to fix. The client sees the result.
• search_client_companiesSearch client companies by name in `q`, with sorting and paging.
• search_clientsSearch clients by text in `q` (name, email, phone or company), with sorting and paging. Use this to find a client's ID before creating a request.
• search_requestsSearch document requests by text in `q`, filter by status and sort. Use this to find a request's ID before other actions.
• search_team_membersSearch team members by text in `q` (name, email, phone or role). Use this to find an owner ID for a request.
• submit_request_for_reviewVisible to othersMark all fields in a request (`request_id`) as submitted for review, on behalf of the client.
• update_clientChanges dataUpdate a client by `customer_id`: name, email, phone, salutation, language or companies. Only the fields you pass change.
• update_requestChanges dataUpdate a request by `request_id`: name, due date, owner, folder or status (draft, published, completed, archived). Only the fields you pass change.

Questions