Respond to ONE received connection request: accept it or decline it. Do not run this without first listing the connection requests to the user (list_connection_requests). Use only after the user has decided specifically what to do, and has named who clearly: a person ("accept Brenda") or a clearly defined group ("decline all the recruiters", "accept everyone from Gitforce"). Never respond on your own initiative, and never just because a request is labelled accept or decline.

For a group, work it out yourself from the list (name, headline, note, message), then call this once per person, one at a time, until you have covered them all. If any request doesn't clearly fit what the user described, skip that one, finish the rest, then ask the user about the skipped ones. If the user asks about something specific, call list_connection_requests once first, then confirm with them which people and which action, so both you and the user know the right operation was requested.

Takes one handle (from list_connection_requests) and action: accept or decline. Synonyms the user may use: accept / approve / add / connect with; decline / reject / ignore / dismiss / turn down; applied to connection requests, invites or invitations. "Ignore" means decline (there is no separate ignore action).

Not instant: each request is queued and answered in the background, spaced out and under a daily limit, to protect the LinkedIn account. After the last one, tell the user once that they'll get an email when it's done. It cannot be undone.

Do NOT use to send or withdraw your own connection requests, or to reply to messages.